This was my reply (in the perldl cc attempt): > <URL: https://rt.cpan.org/Ticket/Display.html?id=66588 > > > On Sun Mar 13 12:35:25 2011, justincase wrote: >> > This article gives a good summary on how to maintain a usable >> > changelog, and the link goes specifically to a comment >> > singling out PDL: >> > > http://blog.urth.org/2011/01/changes-file-how-and-how-not-to.html#comment-32832 > > Thanks for the reference. > With respect to this comment: > > (1) yes, Changes is the git log > (2) these are the developer info > (3) high level change information is Release_Notes > > Personally, my experience with many perl module > Changes file is they are often so minimal as to > be useless. > > Our current approach is, at least, comprehensive. > A plus in my book is that one doesn't need to > know git before one can see development details. > > PDL discussions and support are handled via our > perldl mailing list and the sf.net bug tracker. > I've forwarded this to our perldl list so that > others can discuss further. You may wish > to join in that discussion. > > --Chris >
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
