Re: [pyblosxom-users] pyblosxom 1.5rc2 released!

[will kahn-g. <wi...@bl...>]

On 08/09/2010 04:43 PM, Hauke Fath wrote:
> At 11:05 Uhr -0400 3.8.2010, will kahn-greene wrote:
>> I just release pyblosxom 1.5rc2.  It consists mostly of fixes to
>> plugins, additional tests, and documentation updates.
> 
> I am the maintainer of the pkgsrc py-blosxom package
> <http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/py-blosxom/README.html>. A
> few minor pleas from here:
> 
> Please be consistent in naming the releases (*1.5-rc1 vs. *1.5rc2), and the
> tarball (pyblosxom-*.tgz vs. pybloxsom*.tgz). pkgsrc can work around quirks
> like that, but they makes updating the package lengthier than needs be.

I changed version naming to be valid per the Python version metadata spec:

    http://www.python.org/dev/peps/pep-0386/

This allows versions to be compared correctly when using PyPI and other
tools.  If you check the Pyblosxom/pyblosxom.py file, you'll note that
I've codified the new version scheme that will be used going forward.


> The masters of pkgsrc like to know what's different in an update, so it
> would be helpful if there were release-specific (or at least dated)
> sections in the changelog.

I don't plan on doing this for rc releases.  rc releases are not
considered final and are considered to be unstable.  For now, if you
want to see what's changed, grab the repository and look at "git log".

If someone wants to volunteer to take the notes in git log and convert
them into an appropriate changelog for rc releases, that'd be super,
too.  Just let me know and I'll point you in the right place and we'll
figure out what the workflow should look like.

/will