![\"work](\"https:\/\/owncloud.com\/wp-content\/uploads\/2014\/10\/hacking.png\")
\nThe busy time leading up to the ownCloud release has made it hard to keep up with development. As the value of outdated reports is minimal, this report will merely summarize work done over the last three months, after which we’ll put renewed effort in keeping up by re-instating weekly reports. These will have a reduced area of coverage to make regular updates feasible.<\/p>\n
This report, therefore, covers May and June, focusing on what took place in the core repository of ownCloud<\/a>.<\/p>\n During April, May and June developers were mostly concerned with getting ready for the ownCloud 8.1 release. Since our report on March<\/a> there have been feature additions, but finishing functionality merged during March has been the focus.<\/p>\n In the three months we are covering here there have been over 560 pull requests that were merged in core alone \u2013 with a total of about 1215. As much work outside of the core takes place by direct commit rather than through pull request. It isn’t farfetched to conclude that core might be central to ownCloud, but at least half the work that benefits ownCloud users takes place outside of this repository, in the many apps developed by the ownCloud community. And that is not even covering those apps developed outside of the ownCloud project! Check out the feature overview of ownCloud 8.1<\/a><\/p><\/div><\/p>\n Not all major new ownCloud 8.1 features were in before April 1st. These were merged between April and the end of June:<\/p>\n As a taste of some of the performance-related PR’s, this introduces a stat cache for WebDAV<\/a> and this one cache\u2019s<\/a> language choice<\/a>, while this improvement to the preview class<\/a> helps bring preview generation time up from minutes down to seconds. To allow storage to deal with copy and move commands more efficiently, this PR implements logic to let backends handle these operations<\/a> and this <\/a>PR<\/a> makes it possible to directly access storage when working over WebDAV, saving lots of database accesses.<\/p>\n There has been a lot more of these, one of the reasons why ownCloud 8.1 is significantly faster than previous releases. Another area where a lot of effort was put in over the covered time period was to set up Smashbox for testing ownCloud. Smashbox is an automated testing tool developed by our Atom-smashing friends at CERN<\/a>. We covered this in two blogs introducing Smashbox<\/a> and describing how it is put to use<\/a>.<\/p>\n ownCloud 8.1 has seen quite some work on file locking<\/a>, like the addition of a file lock during download<\/a>. This is part of an effort to make sure ownCloud cannot, even in the weirdest of circumstances, overwrite or lose files (see the many items tagged with feature: locking in github). ownCloud already does file locking to ensure two users can’t access the same file at the same time, but this takes place at the file system level. This will stop one user from overwriting a file being written by another user – but in between separate file operations, such as each individual file being uploaded to a folder, other operations can still take place. If, for example, one user uploads a big file to a folder on external storage which gets renamed by another user at the same time, strange things could happen. The new, high-level locking will ensure that the user who started his\/her endeavor last will receive an error message, while the first user will finish successfully. In case of the sync client, it will automatically retry later.<\/p>\n ownCloud 8.1 introduces high level file locking as an experimental feature which has to be turned on in making the download preview for text look better<\/p><\/div>\n If you want to get involved in coding on ownCloud – check out this page<\/a>!<\/p>\n We published a lot of blogs on Planet ownCloud<\/a> during the last three months:<\/p>\n Please note that if you’re an ownCloud contributor, you should get your blog aggregated on owncloud.org\/news<\/a>! Ping Jos<\/a> with your RSS feed.<\/p>\n We hope you enjoyed this development overview! Stay tuned for an overview of what happened in the first weeks of July.<\/p>\n","protected":false},"excerpt":{"rendered":" The busy time leading up to the ownCloud release has made it hard to keep up with development. As the value of outdated reports is minimal, this report will merely summarize work done over the last three months, after which we’ll put renewed effort in keeping up by re-instating weekly reports. These will have a […]<\/p>\n","protected":false},"author":7,"featured_media":78665,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false,"footnotes":""},"categories":[342,332,333,335],"tags":[],"class_list":["post-8569","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cloud","category-coding","category-community","category-development"],"acf":[],"_links":{"self":[{"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/posts\/8569","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/comments?post=8569"}],"version-history":[{"count":0,"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/posts\/8569\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/media\/78665"}],"wp:attachment":[{"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/media?parent=8569"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/categories?post=8569"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/owncloud.com\/de\/wp-json\/wp\/v2\/tags?post=8569"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Development<\/h2>\n
\n![\"Check](\"https:\/\/owncloud.com\/wp-content\/uploads\/2015\/07\/ownCloud-8.1-image-300x300.png\")
<\/a>New Features<\/h3>\n
\n
Performance work<\/h3>\n
\n![\"cernbox\"](\"https:\/\/owncloud.com\/wp-content\/uploads\/2015\/06\/cernbox.png\")
<\/p>\nSmashbox Testing<\/h3>\n
Locking Work<\/h3>\n
config.php<\/code>. As it is only relevant to very large installations, while being very invasive and recently developed, it was decided to keep it off by default.<\/p>\nMore<\/h3>\n
![\"making](\"https:\/\/owncloud.com\/wp-content\/uploads\/2015\/07\/text-preview-300x169.png\")
<\/a>\n
log_condition<\/code> in config.php<\/code> you can automatically enable debug logging<\/a> (this is documented here<\/a><\/li>\nOther ownCloud Happenings<\/h2>\n
\n