Rename the stable branches to include the major version #2887
Labels
organisation
This is affecting the organisation
Comments
jooola
changed the title
jooola
added
organisation
paddatrapper
pushed a commit
to libretime/website
that referenced
this issue
Jan 13, 2024
### Description Related to libretime/libretime#2887 libretime/libretime@f6d57d5
paddatrapper
pushed a commit
to libretime/website
that referenced
this issue
Jan 13, 2024
### Description Related to libretime/libretime#2887 libretime/libretime@f6d57d5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
We recently changed the way we back port changes to the stable versions (we cherry-pick and apply on top of the target branch). This means we cannot continue to use the non versioned
stablebranch. For example, I cannot merge the current main branch which hold v4, in the stable branch which should hold v3, without breaking the stability promise.With the new back porting strategy, the version branch must diverge, and must not be merged again if the merge would break the stability promise. This requires use to use new version branch names such as
stable-3.xand stable-4.x`.Describe the solution you'd like
The current
stablewill be duplicated to thestable-3.xbranch, and a newstable-4.xwill be created from the latest v4 release.The current
stablebranch (as well asstable-3.x) are now frozen, and will not receive any updates. We recommend you to upgrade to v4.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: