ask 2002/06/04 05:37:46 Modified: . STATUS todo utils.txt Log: useless meta documentation changes. :-) Revision Changes Path 1.2 +11 -2 modperl-2.0/STATUS Index: STATUS =================================================================== RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- STATUS 19 May 2002 09:28:06 -0000 1.1 +++ STATUS 4 Jun 2002 12:37:46 -0000 1.2 @@ -1,11 +1,20 @@ mod_perl 2.0 STATUS: -*-text-*- - Last modified at [$Date: 2002/05/19 09:28:06 $] + Last modified at [$Date: 2002/06/04 12:37:46 $] Release: -------- - 1.99_02-dev: In development. + 1.00_03-dev: In development + 1.99_02-dev: Released June 01, 2002 1.99_01 : Released April 06, 2002 + + + =========================================== + === We are using the todo/ directory to === + === track status; please look there ... === + =========================================== + + Release Showstoppers: --------------------- 1.2 +9 -0 modperl-2.0/todo/utils.txt Index: utils.txt =================================================================== RCS file: /home/cvs/modperl-2.0/todo/utils.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- utils.txt 17 Sep 2001 13:34:54 -0000 1.1 +++ utils.txt 4 Jun 2002 12:37:46 -0000 1.2 @@ -1,6 +1,15 @@ a helper tools/utils that we want/need to have: - Changes files should be autogenerated from cvs logs. + + [ Ask thinks that's a really bad idea; such logs are rarely + useful. Too verbose and nitty gritty detailed for their own good. + "foo->sda fixed to be foo->sdb to fix foogo bug in blah" vs "fixed + foogo bug in blah (patch from C. Ontributor)" + + I have always found the mod_perl change logs very useful and + helpful in the current format. + ] http://www.red-bean.com/cvs2cl/ already does that, but we have an extra wish list: