Tarek Ziadé <ziade.ta...@gmail.com> writes: > On Sun, Nov 29, 2009 at 2:19 PM, Ben Finney <ben+pyt...@benfinney.id.au> > wrote: > > [having the changelog in the package metadata] might be good, if the > > changelog was in a separate file. It's quite commonly a very long > > text file, as it retains the change history of the code base > > indefinitely. > > Yes, and if it's reStructuredText based, we will be able to do what > people do actually, by integrating a reST-based CHANGELOG file at the > end of long_description:
Let's not get ahead of ourselves :-) Asking developers to declare where their changelog file is will be much easier to get than asking them to change the format of that file. Stick to a simple standard of “this file contains the changelog”, which will let people simply move their existing changelog of whatever format into that file. Having it in a predictable location would be a big step forward, and an easy one to enforce. -- \ “Our products just aren't engineered for security.” —Brian | `\ Valentine, senior vice-president of Microsoft Windows | _o__) development, 2002 | Ben Finney _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
