Closed benoitbryon closed 10 years ago
Here are today's proposals :)
Notice that you should be able to easily release the project (if you want to, of course) with make release
(uses zest.releaser) => or, if you do not like this feature, you may remove the "release" parts from the Makefile and tox.ini.
I was looking at make release, not sure how that works? I usually increment version manually in setup.py and init.py and then do a tag.
I usually increment version manually in setup.py and init.py and then do a tag.
That's what zest.releaser helps you to do ;) Bonus: it helps you update dates in CHANGELOG if it can read the format (see http://zestreleaser.readthedocs.org/en/latest/assumptions.html) The tasks are not really complicated, but, as a maintainer of several projects, I really appreciate to have them a bit automated: I no longer have to think about releasing workflow, just answer the questions zest.releaser prompts (defaults are usually good).
Thanks, I'll check it out!
— Zach Kelling $ curl monoid.io/say-hi | python zk@monoid.io / (913) 777-9708
On Sep 15, 2014, at 4:30 PM, Benoît Bryon notifications@github.com wrote:
I usually increment version manually in setup.py and init.py and then do a tag.
That's what zest.releaser helps you to do ;) Bonus: it helps you update dates in CHANGELOG if it can read the format (see http://zestreleaser.readthedocs.org/en/latest/assumptions.html http://zestreleaser.readthedocs.org/en/latest/assumptions.html) The tasks are not really complicated, but, as a maintainer of several projects, I really appreciate to have them a bit automated: I no longer have to think about releasing workflow, just answer the questions zest.releaser prompts (defaults are usually good).
— Reply to this email directly or view it on GitHub https://github.com/zeekay/decorum/pull/7#issuecomment-55662183.
Refs #6