Closed phil-davis closed 11 months ago
It looks like these PRs are in master since https://github.com/owncloud/richdocuments/releases/tag/v2.7.0 was released on 2022-01-20:
should there be a release done "now" and tested against ownCloud core 10.10?
@pmaier1 ?
I guess, in principle it is a good idea to release twice here. 2.8.0 with the accumulated patches before guzzle. 3.0.0 with the above and with guzzle patches.
That way customers who cannot immediately jump to core 10.11 can still get the accumulated updates in richdocuments 2.8.0
Question that I cannot answer: is it worth the effort?
Question that I cannot answer: is it worth the effort?
My opinion is yes, it is worth the effort. But I am not running the show!
I'm happy to create a signed package for Marketplace, when you make a final release tag.
Prepared release-2.8.0 branch for this. And pushed an (unsigned!) RC1 to github for testing: https://github.com/owncloud/richdocuments/releases/tag/v2.8.0-rc.1
Note: there is also code that is updated/added that has correct Symfony calls to work with Symfony4 (now) and Symfony5 (coming with core 10.13). It would be good to get this release done and out before 10.13.
Add @mrow4a 's #493 here too?
@jnweiger yes
3.0.0 was inofficially done (without approval from @timar ) We'll followup with a 3.1.0
we already have richdocuments 4.0.0 released
Reason
@jnweiger Do we need a release of existing changes/fixes? PR #470 adjusts a small piece of code because of Guzzle7-related changes in core for core 10.11. After merging that, the
master
branch will require core 10.11.So, if there is anything needed to release to fix/improve the app with core 10.10 then the release should be done before we merge #470
Product approval
l10n
exists, thengit log
should show '[tx] updated from transifex` ...info.xml
description and screenshotQA
development
toqa
(testplan and tickets mentioned in release ticket)Documentation
Marketing
Build
All actions to be done on the release branch from here:
appinfo/info.xml
(no version suffix)appinfo/info.xml
sonar-project.properties
(no version suffix)Beta/RC
git tag -s v${version}-rc.1
on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)v${version}-rc.1
(see handbook for how to build)HCLOUD_SERVER_IMAGE=debian-10 oc10.sh ...
)Final
v${version}
on release branchPublishing
#updates
channelPost-release
master
branch with description "Closes #XYZ" with the release ticket number$version
and close the milestone