-
-
Notifications
You must be signed in to change notification settings - Fork 281
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
Adopt gitflow for Lodestar releases #4071
Conversation
Some notes from research on other strategies
|
Performance Report✔️ no performance regression detected Full benchmark results
|
From Cayman chat:
|
LGTM! I'm glad this was discussed and planned out. Any issues with having this set up before the first block audit on June 7th? It would be good to have this looked at, especially any parts of the build process that are automated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
(didn't test the CI though)
Co-authored-by: Afr Schoe <58883403+q9f@users.noreply.github.com>
Motivation
Our release process is working okay, but has pain points that are causing trouble and more human error.
Current Lodestar flow
However this had some issues:
We can do some minor changes to our release flow to just do a generic gitflow strategy that fixes this points and fits well our needs.
Description
Switch to gitflow release strategy
Read the new RELEASE.md
➡️ I've marked this issue as discussion and only done the rationale part. Please voice your opinion now, if there's consensus I'll go ahead and update tooling and scripts to automate as much as possible.
Key relevant changes:
master
tounstable
.master
will get retired. Lodestar contributors will use theunstable
branch in the same way they domaster
now.@q9f please comment your opinions as you gave excellent feedback on our current strategy ❤️