Closed juliushaertl closed 2 years ago
Useful commands for getting the PRs:
git log f8be409..master --oneline | grep Merge | grep -v dependabot | grep -v translations
git log v5.3.1..f8be409 --oneline | grep Merge | grep -v dependabot | grep -v translations
Also the milestone https://github.com/nextcloud/nextcloud-vue/milestone/77?closed=1 seems to be still used, even though we have no way to release such a patch release
Useful commands for getting the PRs:
If the changelog for v6-alpha is properly done, then it should also be possible to use this list, including links already. :wink:
The really save option would be to just branch off stable5 from the 5.3.1 release with https://github.com/nextcloud/nextcloud-vue/commit/71e8f2f67b9e35e17b36287e89a1e7dd2a67c596, but I guess the commit you mentioned above before #2704 was merged should also be ok.
This is the changelog from the commit https://github.com/nextcloud/nextcloud-vue/commit/f8be40973a40e28447ba546c1491b27f453469ef
As it includes enhancements I'd still pick it but bump to 5.4 then.
Branched off now, closed the 5.3.2 milestone and moved the PRs accordingly to 5.4 and 6.0. Maybe anyone can check their PRs from the remaining changelog to see if anything needs or should to get backported for a new 5.4 release:
Checked ones are either not necessary or already back ported:
There is a stable5 branch now.
In order to still be able to maintain patch releases we should branch off a stable5 branch before the first breaking change and probably backport fixes in order.
Any objections on this @nextcloud/vuejs ? From my perspective it would still be worth backporting fixes if needed to be able to ship to stable server/app branches.