Skip to content

Documentation for breaking release workflow #477

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

Open
MakisH opened this issue Dec 10, 2024 · 0 comments
Open

Documentation for breaking release workflow #477

MakisH opened this issue Dec 10, 2024 · 0 comments
Labels
content Content-only issues

Comments

@MakisH
Copy link
Member

MakisH commented Dec 10, 2024

Do we already have a section where we explain the general workflow for a breaking release? > This is not directly related to the schedule but I think it would be helpful to at least point to this workflow from here.

Some points that are important in my opinion:

  • What we did last time: At some point there was a v3_develop branch in parallel to the develop branch. At some later point we decided to merge v3_develop into develop. This closed the door for any v2 releases and forced everybody to integrate new features directly with v3.
  • I think it would also be helpful to point to the milestone that we usually create in order to cluster breaking releases way before the breaking release is scheduled (see https://github.com/precice/precice/milestone/20).

Originally posted by @BenjaminRodenberg in #475 (comment)

@MakisH MakisH added the content Content-only issues label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Content-only issues
Projects
None yet
Development

No branches or pull requests

1 participant