-
Notifications
You must be signed in to change notification settings - Fork 42
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
SPEC10 on release documentation #242
Comments
I think we agreed on the following:
Ways to do change log:
|
Thanks for taking on this topic. It'd be interesting to see what coalesces out of all the opinions. Re principle 2, I'd say leave decisions of what to include to the project. There are some essentials (API changes etc.) but then doc updates etc. will depend on how fine grained the project wishes to be. |
Saw this in ics-py release notes: https://keepachangelog.com/en/1.0.0/ |
Does this mean our work is done? Hard for me to tell who wrote that though. |
Re who wrote it, you can find the repo and its author here https://github.com/olivierlacan/keep-a-changelog. |
IMHO it still would be helpful to have a dedicated SPEC to bring visibility to this topic in our ecosystem. |
As discussed briefly during Scipy 2023. cc @bsipocz @lagru
after all we were asked for opinionated ideas
becareful what you wish for
Might be useful. Even if just to collect/build community consensus what should be present in release notes and how best to achieve that!
The text was updated successfully, but these errors were encountered: