Create release branch for Popochiu 1.x and adopt a release-based branching model #14
Closed
3 tasks done
Labels
improvement
New feature or request
Milestone
Related to #12 and the Popochiu 2.0 milestone in general, we decided 1.x will go on maintenance. New releases may contain a bunch of backported features but main development will happen on 2.0.
The following should happen on
popochiu-dev
, which at the moment has no tags (this is strictly related to #13 and is another undesirable effect of the separation of development and release branches, in my opinion):develop
, in case Smoothen release workflow #13 is done) to amaintenance/1.x
branch1.8.4
release on that branch so that subsequent released will be tagged on the maintenance branchThe development on the
main
/develop
branch will always be on the more recent version (2.0 at the time of writing)The text was updated successfully, but these errors were encountered: