Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Branch off stable5 #2907

Closed
juliushaertl opened this issue Aug 1, 2022 · 7 comments
Closed

Branch off stable5 #2907

juliushaertl opened this issue Aug 1, 2022 · 7 comments

Comments

@juliushaertl
Copy link
Contributor

juliushaertl commented Aug 1, 2022

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.

@juliushaertl
Copy link
Contributor Author

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

@juliushaertl
Copy link
Contributor Author

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

@jotoeri
Copy link
Contributor

jotoeri commented Aug 2, 2022

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. 😉

@raimund-schluessler
Copy link
Contributor

The really save option would be to just branch off stable5 from the 5.3.1 release with 71e8f2f, but I guess the commit you mentioned above before #2704 was merged should also be ok.

@juliushaertl
Copy link
Contributor Author

This is the changelog from the commit f8be409

As it includes enhancements I'd still pick it but bump to 5.4 then.

Unreleased (2022-08-02)

🚀 Enhancement

🐛 Bug Fix

@juliushaertl
Copy link
Contributor Author

juliushaertl commented Aug 2, 2022

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:

🐛 Fixed bugs

@raimund-schluessler
Copy link
Contributor

There is a stable5 branch now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants