db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: Versioning, contents of STATUS and CHANGES files
Date Wed, 19 Jan 2005 19:03:22 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rodent of Unusual Size wrote:

>
> Have there been no changes to the code since the release of 10.0.2.1?
> If there have been, they should be getting recorded in the trunk/CHANGES
> file, at the top, under a heading such as
>
> Changes in Derby 10.0.2.2-dev
>
> (or whatever version number is being used/embedded to identify
> the code as alpha/beta).  At the 10.0.2.2 release, that gets altered
> to 'Changes with 10.0.2.2' and a new 'Changes with 10.0.2.3-dev'
> heading is started above it.  Otherwise the CHANGES file won't change
> except at releases, which is a disservice to people observing or
> getting involved in the development mid-stream.

Can the contents of the CHANGES files (for the trunk and each branch) be
created automatically from the svn commit log. It's a little tedious and
error prone to have to update something manually, when it could be
automated.

Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFB7q76Iv0S4qsbfuQRAjPDAJ4pytp7C+UrSFh3ijwIEMujPF0tBACgyeqi
FPYGb7p42y8ueEeZl9PAJZM=
=toKe
-----END PGP SIGNATURE-----


Mime
View raw message