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

move NEWS to HISTORY #57256

Merged
merged 1 commit into from
Feb 6, 2025
Merged

move NEWS to HISTORY #57256

merged 1 commit into from
Feb 6, 2025

Conversation

KristofferC
Copy link
Member

No description provided.

@KristofferC KristofferC added the release Release management and versioning. label Feb 4, 2025
@KristofferC KristofferC changed the title Kc/move news to history move NEWS to HISTORY Feb 4, 2025
@nsajko nsajko added the docs This change adds or pertains to documentation label Feb 4, 2025
@KristofferC KristofferC force-pushed the kc/move_NEWS_to_HISTORY branch from de5a72e to 7f7ef3b Compare February 6, 2025 12:06
@KristofferC KristofferC merged commit 7621dc5 into master Feb 6, 2025
4 of 7 checks passed
@KristofferC KristofferC deleted the kc/move_NEWS_to_HISTORY branch February 6, 2025 15:22
@Keno
Copy link
Member

Keno commented Feb 6, 2025

If I have unmerged 1.12 changes that touch NEWS, should I rebase them to touch HISTORY instead and then you can resolve it on the backport or just drop the NEWS change and do a separate NEWS PR to 1.12?

@KristofferC
Copy link
Member Author

Just edit HISTORY, I can resolve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation release Release management and versioning.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants