-
Notifications
You must be signed in to change notification settings - Fork 168
10.0.4 release notes draft #3533
Changes from 9 commits
0943751
7543ea8
f6d6301
5b4279c
1a95557
3841684
cc15df3
0115865
ea8475c
202b283
06b95c5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,7 @@ | |
Release Notes | ||
============= | ||
|
||
* :ref:`10.0.4_release_notes_label` | ||
* :ref:`10.0.3_release_notes_label` | ||
* :ref:`10.0.1_release_notes_label` | ||
* :ref:`10.0.0_release_notes_label` | ||
|
@@ -12,6 +13,65 @@ Release Notes | |
* :ref:`8.0_release_notes_label` | ||
* :ref:`7.0_release_notes_label` | ||
|
||
.. _10.0.4_release_notes_label: | ||
|
||
Changes in 10.0.4 | ||
----------------- | ||
|
||
Dear ownCloud administrator, please find below the changes and known issues in ownCloud Server 10.0.4 that need your attention: | ||
|
||
**The full ownCloud Server 10.0.4 changelog can be found here: https://github.com/owncloud/core/blob/stable10/CHANGELOG.md** | ||
|
||
* **More granular sharing restrictions** | ||
The "*Restrict users to only share with users in their groups*" option, in the Sharing settings, restricts users to only share with groups which they are a member of, while simultaneously prohibiting sharing with single users that do not belong to any of the users' groups. | ||
To make this more granular, we split this option into two parts and added "*Restrict users to only share with groups they are member of*", which differentiates between users and groups. Doing so makes it possible to restrict users from sharing with all users of an installation, limiting them to only being able to share with groups which they are a member of, and vice versa. | ||
|
||
- **Configurable solution for indistinguishable user display names** | ||
The ownCloud sharing dialog displays users according to their display name. As users can choose their display name in self-service (which can be disabled in `config.php`) and display names are not unique, it is possible that a user can't distinguish sharing results. To cover this case the displayed user identifiers are now configurable. In the Sharing settings administrators can now configure the display of either mail addresses or user ids. | ||
|
||
- **Added "occ files:scan" repair mode to repair filecache inconsistencies** | ||
We recommend to use this command when directed to do so in the upgrade process. | ||
Please check the ownCloud documentation for more information (https://doc.owncloud.com/server/10.0/admin_manual/configuration/server/occ_command.html?highlight=occ#the-repair-option). | ||
|
||
- **Detailed mode for "occ security:routes"** | ||
Administrators can use the output of this command when using a network firewall, to check the appropriateness of configured rules or to get assistance when setting up. | ||
|
||
- **Added mode of operations to differentiate between single-instance or clustered setup** | ||
As ownCloud needs to behave differently when operating in a clustered setup versus a single instance setup, the new `config.php` option `operation.mode` has been added. It can take one of two values: `single-instance` and `clustered-instance`. | ||
For example: | ||
|
||
``` | ||
'operation.mode' => 'clustered-instance', | ||
``` | ||
|
||
Currently the Market App (ownCloud Marketplace integration) does not support clustered setups and can do harm when used for installing or updating apps. The new config setting prevents this and other actions that are undesired in cluster mode. | ||
**Therefore when operating in a clustered setup it is mandatory to set this option.** | ||
Please check the ownCloud documentation for more information (https://doc.owncloud.com/server/10.0/admin_manual/configuration/server/config_sample_php_parameters.html#mode-of-operation). | ||
|
||
- **Added occ dav:cleanup-chunks command to clean up expired uploads** | ||
When file uploads are interrupted for any reason, already uploaded file parts (chunks) remain in the underlying storage so that the file upload can resume in a future upload attempt. | ||
However, resuming an upload is only possible until the partial upload is expired and deleted, respectively. To clean up chunks (expire and delete) originating from unfinished uploads, administrators can use this newly introduced command. The default expiry time is two days, but it can be specified as a parameter to the command. | ||
**It is recommended to configure CRON to execute this background job regularly**. It is not included in the regular ownCloud background jobs so that the administrators have more flexibility in scheduling it. Please check the ownCloud documentation for more information (https://doc.owncloud.com/server/10.0/admin_manual/configuration/server/background_jobs_configuration.html#cleanupchunks). | ||
|
||
- **Administrators can now exclude files from integrity check in config.php** | ||
When administrators did intentional changes to the ownCloud code they now have the ability to exclude certain files from the integrity checker. | ||
Please check "config.sample.php" for the usage of ``'integrity.excluded.files'``. | ||
|
||
- **Modification time value of files is now 64 bits long** | ||
Note: When upgrading to 10.0.4 migrations may increase update duration dependent on number of files. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can't this be done without downtime ... we really should think about a strategy for doing this ... probably with a new table that gets renamed after the column has been changed ... this will take hours on large installations There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not the right place to ask |
||
|
||
- **Updated minimum supported browser versions** | ||
Note: Users with outdated browsers might get warnings. See the list of supported browser versions: https://doc.owncloud.com/server/10.0/admin_manual/installation/system_requirements.html#web-browser | ||
|
||
- **10.0.3 known issues are solved** | ||
- SFTP external storages with key pair mode work again | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should we add links to resolved tickets ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep. It's great for transparency. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added. |
||
- Added support for MariaDB 10.2.7+ | ||
- Encryption panel in admin settings fixed to properly detect current mode after upgrade to ownCloud 10 | ||
|
||
**Known issues** | ||
|
||
Currently there are no known issues for ownCloud Server 10.0.4. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we remove this section ? This seems to state that ownCloud 10.0.4 is bug-free which is not correct 😄 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As no software's bug-free, I'd say yes. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As I said above I left the section not to confuse people that we might have missed to add it. This way it states that there are no issues that we consider as "known" and "to-be-fixed". Should we remove it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, I'd leave it. It's clear in what it says, and it's honest. |
||
|
||
.. _10.0.3_release_notes_label: | ||
|
||
Changes in 10.0.3 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AKA how to shoot yourself in the foot ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now that you mention it I'm not 100% that it works that way.
the original purpose was to exclude non-OC files (often server specific hidden files) that people have lying around inside the OC folder.
need to test whether excluding already signed files from integrity check works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree to @PVince81
would not state this as the reason for having that implemented which is different to this text.
(Do not open Pandoras Box...)
Please see the link to get an impression of: https://github.com/owncloud/core/pull/29126/files
Please reference to the documentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have tested this with the 10.0.4RC1 tarball and can confirm that you can exclude patched files from integrity check as well as any new file that you might have created. So the description is good.