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

Release notes for 4.0.x, x > 0, are missing #2913

Closed
dhendriks opened this issue Oct 12, 2023 · 4 comments · Fixed by #2920
Closed

Release notes for 4.0.x, x > 0, are missing #2913

dhendriks opened this issue Oct 12, 2023 · 4 comments · Fixed by #2920

Comments

@dhendriks
Copy link
Contributor

See https://github.com/eclipse-tycho/tycho/blob/16eba006183677d3ee5db10d0da839f905fcec18/RELEASE_NOTES.md. The release notes for 3.0.0, 3.0.1, etc are present. 4.0.0 is present, but not 4.0.1 etc. The draft for 5.0.0 is present. I miss 4.0.1, 4,0.2, etc, which have already been released. I see their release notes in their tags, but on master.

@laeubi
Copy link
Member

laeubi commented Oct 12, 2023

@dhendriks usually these are copied after a release but as we usually have only Bugfixes now there is not much "new", anyways if you like you can just open a PR to sync these into the master as well.

@dhendriks
Copy link
Contributor Author

For 3.0.x it was included as well, even if it was only bugfixes/backports. Also, it is not only bugfixes/backports, see e.g. https://github.com/eclipse-tycho/tycho/blob/tycho-4.0.2/RELEASE_NOTES.md, which indicates 'new option to include referenced repositories when resolving the target platform'. Isn't it just good practice to have a complete overview of all the releases and their changes?

@laeubi
Copy link
Member

laeubi commented Oct 12, 2023

As said, simply open a PR to copy over the parts from 4.x > master branch :-)

@dhendriks
Copy link
Contributor Author

As said, simply open a PR to copy over the parts from 4.x > master branch :-)

Fine, I've created #2920. Note that I don't think I should be doing this every time. I think whomever makes a release should do this.

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

Successfully merging a pull request may close this issue.

2 participants