Initial draft (Ref. T982)
Details
- Reviewers
vanmeeuwen - Group Reviewers
Documentation Authors - Maniphest Tasks
- T982: Add an upgrade guide from Kolab:3.4 to Kolab:16
- Commits
- rDfbfa137f3565: Initial draft the upgrade guide to Kolab 16
rD68e5d1017206: Initial draft the upgrade guide to Kolab 16
None in particular
Diff Detail
- Repository
- rD docs
- Branch
- T982
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 2726 Build 2643: arc lint + arc unit
Event Timeline
I'm missing the reference from source/upgrade-guide/index.rst.
See further commentary as well.
source/upgrade-guide/kolab-16.rst | ||
---|---|---|
3 | The header is superfluous and not used in other upgrade guides either. If the header persists, please ensure that it is globally unique, like "upgrade-guide-kolab-3.4-to-16" | |
7 | Other guides use: Upgrade Notes from Kolab 3.4 to 3.5 implying that the "CentOS 7" part is a given. | |
20 | This should have already happened as a prerequisite for the installation of Kolab 3.4. | |
27 | I'm missing the step where the Kolab:3.4 and Kolab:3.4:Updates repositories are removed. | |
33 | This should have already happened as a prerequisite for the installation of Kolab 3.4. | |
39 | This should have already happened as a prerequisite for the installation of Kolab 3.4. | |
57 | This may need to become: .. parsed-literal:: # :command:`yum shell` > :command:`remove php-mysql` > :command:`install php-mysqlnd` > :command:`run` (Confirm as requested) > :command:`exit` | |
82 | It seems this is a wrong reference. |
These look good.
You are going to create a supplemental segment on updating configuration files, right?
Thanks!
source/upgrade-guide/kolab-16.rst | ||
---|---|---|
69 | Please use a capital 'C'. | |
72 | Please use "After upgrading the packages", correct typo. | |
100 | These last two steps for Guam and Manticore can be moved to be the first two steps, since they are free of charge and have no impact. That way, in sort of like an intermezzo new paragraph, you can re-iterate that if people are still using all defaults, they can execute the setup-kolab roundcube command (which requires the correct password for the current roundcube database user), and the setup-kolab imap command. If not running with defaults, copy off the original (current) configuration so they can compare later and re-apply their changes to the newly generated configuration files. |
- Changes made after review.
- Added section about configuration update
- Updated section about configuration. Added warning about mysql error