[Grok-dev] Re: making releases to PyPI
Brandon Craig Rhodes
brandon at rhodesmill.org
Tue Mar 18 17:55:48 EDT 2008
Martijn Faassen <faassen at startifact.com> writes:
> Brandon Craig Rhodes wrote:
>> Martijn Faassen <faassen at startifact.com> writes:
> It's actually not as long a release procedure as it sounds.
Were it two steps, I'd script it. :-)
> Some of this involves some manual checking (the documentation
The script will either, for example, report that the section for the
new version is missing entirely from CHANGES.txt, or if it instead
successfully finds it, will display the relevant section from
CHANGES.txt and refuse to go further until the user has typed "yes"
that they like the description and think it fits what they're
In the first instance, where it finds the section missing, it will
probably helpfully print what a sample CHANGES.txt stanza looks like,
and maybe print out an "svn log" of the changes made to the code base
since the last update to "CHANGES.txt" itself. It would even pre-
format them under indented asterisks to make pasting them into
CHANGES.txt and then editing them as easy as possible.
Brandon Craig Rhodes brandon at rhodesmill.org http://rhodesmill.org/brandon
More information about the Grok-dev