-
Notifications
You must be signed in to change notification settings - Fork 20
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
Introduce a develop
branch?
#92
Comments
Sounds like a good suggestion to me! |
Do you know how we can proceed with that? Probably that's:
|
Personal opinion, I think it would be better to keep main as the development branch. Upload the build of main to the Inria nightly build server, same as the TLA+ tools. Keep the commits flowing into main and don't worry too too much about the odd bug, use releases to mark certain commits as stable when appropriate. See PR #96 |
I'm not arguing in favor of adding or removing branches, but merely want to bring up the idea of rolling releases. |
One obstacle to rolling releases is that the current head of the main branch does not do well on the tlaplus/examples corpus: https://github.com/tlaplus/tlapm/actions/runs/6680011626/job/18152686044 |
Paging @damiendoligez and @muenchnerkindl. |
I have no objection. |
Okay who has the permissions to make this change? |
"ahelwer has been added as a collaborator with maintain permissions on the repository." |
This does give me the ability to draft new releases but I don't have access to CI settings. The "Code and automation" setting panel. |
This is not relevant anymore. Let's use the main branch. |
Maybe it would be easier to integrate different changes if TLAPM had a
develop
branch along with themaster
(ormain
)?In such a case, all the pull requests should be based on the
develop
branch and be merged first back to it. While the main branch is expected to be stable, thedevelop
could have all the ongoing changes integrated and tested together. When the code quality in thedevelop
branch is deemed ready for a release, it could be merged into themaster
, and a release would be produced based on it.The text was updated successfully, but these errors were encountered: