Skip to content

Add empty release notes for 0.6.3 #757

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
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

Czaki
Copy link
Contributor

@Czaki Czaki commented Jul 1, 2025

References and relevant issues

Description

To avoid problems with lack of release notes on first napari 0.6.3 alpha just add empty release notes.

@Czaki Czaki added this to the 0.6.3 milestone Jul 1, 2025
@Czaki Czaki added the documentation Improvements or additions to documentation label Jul 1, 2025
@TimMonko
Copy link
Contributor

TimMonko commented Jul 1, 2025

@jni @Czaki do you think it would be better to instead encourage Release Managers to make not empty release notes, but run the script on the next milestone?

Thinking ahead to what we can add to #755 ...

Thinking about it more, it's better that release notes don't include speculative PRs, because it would make something like an early alpha confusing when reading the notes because of uncertainty on what's actually been changed.

@Czaki
Copy link
Contributor Author

Czaki commented Jul 1, 2025

@jni @Czaki do you think it would be better to instead encourage Release Managers to make not empty release notes, but run the script on the next milestone?

Since at least 3 releases, the release manager forgot to do this and the first alpha was not released.

Thinking about it more, it's better that release notes don't include speculative PRs

I agree

@TimMonko TimMonko mentioned this pull request Jul 1, 2025
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants