See this thread: https://groups.google.com/d/msg/sympy/qkP3WAuWwbc/k3mi2NDea9MJ
In my view, we should adopt some tagging for merge commits (e.g. with pr headers). This can help us with automatic generation of the release notes. Something like the scipy project. Take for example our last release notes or scipy's doc/release/0.15.0-notes.rst. Both have: 1) new features 2) bugfixes 3) deprecations 4) backward-incompatible changes We should divide our pr's to such or similar categories. Also, list of closed issues in the given release - great feature for next changelog. Automatic generation of the release notes will be trivial if we adopt the above mentioned tagging and this syntax for closing issues: https://help.github.com/articles/closing-issues-via-commit-messages/ Sure, it will require a manual intervention from the release manager, but others can help. We can add old release notes retroactively (at least, for the code history in our git tree). On Friday, November 21, 2014 7:12:14 PM UTC+3, Jason Moore wrote: > > We keep track of our release notes on the wiki. To me, it seems like these > should be in a file included with the source code so it always travels with > the git repo and our source distributions. It would also be nice if every > pull request with significant changes had to include a change to the > changelog file. A check to see if the changelog file was modified in a PR > could be done on with travis too. > > Are there reasons that the wiki is preferred? > > Jason > moorepants.info > +01 530-601-9791 > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/d9d4490b-a339-484a-bbfb-16c24d3e46e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
