Discussion : Change to the release process #4263
Merged
Conversation
This file contains 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
Pierre-Sassoulas
added
Discussion 🤔
Documentation 📗
Maintenance
Pierre-Sassoulas
requested review from
hippo91,
AWhetter,
brycepg and
PCManticore
Pierre-Sassoulas
changed the title
|
@Pierre-Sassoulas that's a good question. IMHO, i think that we should chose the option that corresponds to as few work as possible for us because we do not have enough free time for that. |
4 tasks
Pierre-Sassoulas
force-pushed
the
change-release-process
branch
2 times, most recently
from
3ac8781
to
42198a5
Compare
Pierre-Sassoulas
force-pushed
the
change-release-process
branch
2 times, most recently
from
2d46059
to
3ce4187
Compare
Pierre-Sassoulas
force-pushed
the
change-release-process
branch
2 times, most recently
from
af03f4a
to
139cd71
Compare
Pierre-Sassoulas
changed the title
Pierre-Sassoulas
force-pushed
the
change-release-process
branch
2 times, most recently
from
6484bfc
to
db8a43c
Compare
Pierre-Sassoulas
force-pushed
the
change-release-process
branch
from
db8a43c
to
c4dcbdf
Compare
Merged
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.
Description
For
2.7.3we had 100 commits to triage with 10 commits or so to remove and 5 conflicts to resolve. I think we did not release fast enough because of #4206 but even so, the release process seems a little tedious for not much value added. Maybe if we release often enough we won't have a swarm of bug coming our way when we do release ? The question then become when do we release a major ? When there is enough new functionalities ? Or should we cherry-pick in 2.x branch every time we merge something ? It's still time consuming. Should we squash every merge request so it's easier to cherry pick afterwards?Type of Changes