Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
On Fri, Dec 02, 2005 at 02:14:30PM -0500, Chris Shoemaker wrote:
My preferred implementation of the policy change is currently:
- Continue the pattern Christian started of pulling old ChangeLog
entries into archive files. These files would continue to live in svn.
BTW, I think that for every public release we should also archive the
ChangeLog at that time. (That doesn't preclude also archiving for any
other occasion.) It doesn't matter to me that the archive files are
named after years. If we release version 2.1.1 on Oct. 2, 2006, then
the ChangeLog up to that release should move from "generated-land" to
"archive-land" (ChangeLog.2006) at the same time.
I disagree.. If you want to say that it gets rotated at every major/minor
release (e.g. 1.6, 1.8, 2.0) that's fine. I do not believe that we should
rotate between e.g. 2.0.0 and 2.0.1.
- The "newest" ChangeLog file would be a generated file, made during
"make dist", and "make ChangeLog". It would be generated thusly:
$ svn log -v --xml -r BASE:12076 | xsltproc \
--stringparam strip-prefix "gnucash" --stringparam
include-rev "yes" \
./svn2cl.xsl - > ./ChangeLog
I had to tweak this a bit to get all branches included. My plan is to
commit something like this soon that actually generates ChangeLog.svn
(not ChangeLog). Then, the next time we rotate the ChangeLog (either
for a release or for New Years), I want to archive the existing log
and make new entries "generated". At that time, the generated file
will be called ChangeLog.
I would prefer if you refrained at this moment.. I don't think we have
consensus on this change, yet.
-chris
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
