richdocuments 2.7.0 #427
Description
Release 2.7.0
Reasons
- ownCloud Web compatibility Added new route for obtaining docInfo from fileId #423
- Support for Draw added Diagram document type to + button #436
- Fix broken upload Make upload work again #437
Product approval
- Verify transifex commits are in master: If a folder https://github.com/owncloud//tree/master/l10n exists, then https://drone.owncloud.com/owncloud/ should receive nightly '[tx] updated from transifex` ...
- Ping pmaier to check
info.xmldescription and screenshot - Get approval on translations from pmaier - send the date of the last tx commit from drone to Patrick
QA
- Create QA Milestone and set the description to $version
- Move tickets from milestone
developmenttoqa(testplan and tickets mentioned in release ticket) - Create release branch with the format "release-$version"
- Create "$version Testplan" (QA templates or Enterprise) -> [QA] 2.7.0 Testplan #440
- copy new/reopened issues from the previous release ticket as 'Issues to review' below.
- XXX check if Non-normal Release Process applies, and adapt this checklist. release build and upload by Collabora!
Documentation
- Update oC Web documentation on how to use Collabora Online with oC Classic backend (https://owncloud.dev/clients/web/deployments/oc10-app/#integrate-owncloud-classic-features-in-owncloud-web)
[docs-only] Add Collabora Online with oC Classic configuration to docs web#6282
Marketing
- Ping @owncloud/marketing
- Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
- Request a screenshot if the app is new or changed fundamentally
- Include in oC Web release communication
Build
- build done by Collabora
- Check version number in info.xml
- check Changelog
Beta/RC
- Manual explorative testing:
- Changelog testing
- Test and document in testplan => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch
Final
- Check that no documentation issues are pending
- Send Go Ahead to Collabora
Publishing
- Collabora uploads tarball to marketplace
Post-release
- Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
- Create PR to merge changes back to the
masterbranch with description "Closes #XYZ" with the release ticket number - Rename QA milestone to
$versionand close the milestone - Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
- Ensure release template is up to date
- Ensure the testplan template (community or enterprise) is up to date
- Close the testplan issue