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

Keeping a nice changelog #2463

Open
mhauru opened this issue Jan 13, 2025 · 8 comments
Open

Keeping a nice changelog #2463

mhauru opened this issue Jan 13, 2025 · 8 comments

Comments

@mhauru
Copy link
Member

mhauru commented Jan 13, 2025

@seabbs pointed out that it could be helpful to have a place to check changes in recent versions. I think @penelopeysm recently mentioned something similar, about how it could be good practice to type some human-readable change notes at least for all breaking releases. I think this could be a good idea, have them as part of GitHub releases if nothing else. An example of how epinowcast is doing theirs: https://package.epinowcast.org/news/index.html

@penelopeysm
Copy link
Member

If you trigger JuliaRegistrator with release notes, it gets automatically added to the github release, I did this for the two latest versions of DynamicPPL: https://github.com/TuringLang/DynamicPPL.jl/releases

@penelopeysm
Copy link
Member

Slightly frustratingly, JuliaRegistrator expects a really precise format for the release notes that is (as far as I know) not documented. For minor version bumps it has to look like this

@JuliaRegistrator register

Release notes:

## Breaking changes

- Foo
- Bar

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/122924

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.36.0 -m "<description of version>" 7d6f8ed53b59047c86fb1c09c9d593ca30250a60
git push origin v0.36.0

@penelopeysm
Copy link
Member

Oh, for goodness' sake.

@mhauru
Copy link
Member Author

mhauru commented Jan 13, 2025

Hahaha, it's so eager to help.

@seabbs also pointed out that having one centralised place for all the packages in the ecosystem might be good. Maybe an autogenerated page of turinglang.org that lists all new releases of all of our packages?

@penelopeysm
Copy link
Member

I think that's this TuringLang/turinglang.github.io#104

@seabbs
Copy link

seabbs commented Jan 13, 2025

Love the bot fighting back here. In terms of a central place I meant a single place for release notes/turing news etc kind of like this https://www.tidyverse.org/blog/ its a big effort though and we don't do a good job of it in epinowcast land (i.e we did it once for one package https://www.epinowcast.org/blog.html).

@penelopeysm
Copy link
Member

That would be really cool. I know there was some kind of attempt at having a blog https://turinglang.org/news/ but that predates our time on the project

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

No branches or pull requests

4 participants