On Tue, Jun 30, 2009 at 12:49:36PM -0700, David E. Wheeler wrote: > On Jun 30, 2009, at 12:12 PM, Nicholas Clark wrote: > > =item New Tests > > > > Changes which create B<new> files in F<t/> go here. Changes to > >existing files > > in F<t/> aren't worth summarising, although the bugs that they > >represent > > may be. > > > > > >As above. > > > >3: Search for lines matching m!t/.*\.t! (and I think in ext/ > >DynaLoader) > > > >6: For each file only in the newer MANIFEST > > a: Grab the description line from MANIFEST > > b: Write out an =item section with the filename, and description, > >just > > like > > http://perl5.git.perl.org/perl.git/blob/maint-5.10:/pod/perl5101delta.pod > > Hrm. Why track test changes? Does the end user who's interested in > what's changed since the last version really care? I'm not sure, but I think it's a: publicity for "we have tests". b: a note that "this regression test is new, so if it fails for you, and you didn't see it fail on the previous version, that's not because something broke" It's only at the level of entire new files. Nicholas ClarkThread Previous | Thread Next