koji: Add supported git branches (eg: [8.3, master] for v8.3-* tags) #774
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rzr
force-pushed
the
phcoval/review/master
branch
from
05da6b2 to
e8eb4fb
Compare
make `koji_build` accept builds for v8.3 and from both `master` and `8.3` Preparation for switch `master` to be "next" aka v9 To my understanding, the motivation of change is part of a bigger plan, to prepare a smooth transition to enable bleeding edge development on master branch. Of course maintenance will remain in v8.x branches. Once the master branch needs to be stabilized then a new 9.0 branch can be open (this mean declared in PROTECTED_TARGETS, and also move the `master` branch from `8.3` target to `9.0` for a future cycle) Meanwhile the development on master is still open and might become the base for the next cycle (TBD 9.1 or 10). Note that `8.3` git branches are not created yet in repos, it would make sense to open them soon or later, ideally when master branches need to receive feature from next release. Coincidentaly thoses 8.3 branches will be used for maintenance of the LTS release and then developers/RE might consider back-porting fixes from master to 8.3. What is unclear to me in the plan is when the new koji target/tag v9 will be defined, or if an `unstable` target will be added before, probably this will have to be coordinated with CI. Signed-off-by: Philippe Coval <philippe.coval@vates.tech>
rzr
force-pushed
the
phcoval/review/master
branch
from
e8eb4fb to
b07bb55
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
make
koji_buildaccept builds for v8.3 and from bothmasterand8.3Preparation for switch
masterto be "next" aka v9To my understanding, the motivation of change is part of a bigger plan, to prepare a smooth transition to enable bleeding edge development on master branch. Of course maintenance will remain in v8.x branches.
Once the master branch needs to be stabilized then a new 9.0 branch can be open (this mean declared in PROTECTED_TARGETS, and also move the
masterbranch from8.3target to9.0for a future cycle)Meanwhile the development on master is still open and might become the base for the next cycle (TBD 9.1 or 10).
Note that
8.3git branches are not created yet in repos, it would make sense to open them soon or later, ideally when master branches need to receive feature from next release. Coincidentaly thoses 8.3 branches will be used for maintenance of the LTS release and then developers/RE might consider back-porting fixes from master to 8.3.What is unclear to me in the plan is when the new koji target/tag v9 will be defined, or if an
unstabletarget will be added before, probably this will have to be coordinated with CI.