Skip to content
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

Setup for v2.2 development #2439

Merged
merged 3 commits into from
Jul 27, 2024
Merged

Setup for v2.2 development #2439

merged 3 commits into from
Jul 27, 2024

Conversation

MatthewDaggitt
Copy link
Contributor

@MatthewDaggitt MatthewDaggitt commented Jul 17, 2024

After this is merged, we can start merging in v2.2 PRs.

@MatthewDaggitt MatthewDaggitt added this to the v2.2 milestone Jul 17, 2024
CHANGELOG/v2.1.md Outdated Show resolved Hide resolved
Copy link
Contributor

@jamesmckinna jamesmckinna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides @gallais 's suggestion, I think that this looks good to go.

Co-authored-by: G. Allais <guillaume.allais@ens-lyon.org>
@MatthewDaggitt MatthewDaggitt added this pull request to the merge queue Jul 27, 2024
Merged via the queue into master with commit 6f1416b Jul 27, 2024
11 checks passed
@MatthewDaggitt MatthewDaggitt deleted the move-to-v2.2 branch July 29, 2024 02:48
@jamesmckinna
Copy link
Contributor

jamesmckinna commented Jul 29, 2024

Should we also update the release-guide.md to document this (new) workflow/branch discipline... and set in stone blessed names for these 'release' branches... cf. #2444 ?

@JacquesCarette
Copy link
Contributor

Makes sense to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants