Hi Bruno, due to its Nature its best suited for introducing right after 3.1
after all the before bits are already in place -- Ronny On 21.03.2017 14:41, Bruno Oliveira wrote:
Hi Ronny, I definitely like the idea! I agree our current CHANGELOG maintenance could use some improvement. :) We could introduce it for `3.1`, what do you think? On Tue, Mar 21, 2017 at 5:54 AM Ronny Pfannschmidt <opensou...@ronnypfannschmidt.de <mailto:opensou...@ronnypfannschmidt.de>> wrote: Hi all, today i noticed how pip manages its change-logs in a pretty interesting way, they manage the fragments to be composed before a release in the folder "news" in files named like "$ticketnumber.$changetype" before a release those files get take out and composed into the change-log. The fabulous tool behind that is https://github.com/hawkowl/towncrier/ - after taking a first look at it, i believe it should be a massive enhancement compared to what we put ourselves trough right now. i also would be delighted, if we used it in more projects ^^ cheers, Ronny _______________________________________________ pytest-dev mailing list pytest-dev@python.org <mailto:pytest-dev@python.org> https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
