Skip to content

Conversation

ariostas
Copy link
Collaborator

This is still in draft since I want to confirm the timeline and make sure that it's not too noisy.

@ianna ianna added the next-release Required for the next release label Aug 28, 2025
@ariostas ariostas marked this pull request as ready for review September 4, 2025 20:32
@ariostas ariostas requested a review from ianna September 4, 2025 20:32
@ariostas
Copy link
Collaborator Author

ariostas commented Sep 5, 2025

Apart from version number should we also mention a rough date on the timeline? Maybe just "early 2026"?

Copy link
Collaborator

@ianna ianna left a comment

Choose a reason for hiding this comment

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

@ariostas - great! Thanks.

@ianna ianna enabled auto-merge (squash) September 5, 2025 19:53
@ianna ianna merged commit a39f72e into main Sep 5, 2025
26 checks passed
@ianna ianna deleted the ariostas/warn_rntuple_by_default branch September 5, 2025 20:17
@ianna
Copy link
Collaborator

ianna commented Sep 6, 2025

Apart from version number should we also mention a rough date on the timeline? Maybe just "early 2026"?

I think it’s better if we just have a release timeline perhaps on a discussion?

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

Successfully merging this pull request may close these issues.

2 participants