OK, now that 7.7 is open for business, how about a "rule" that developers that add or change functionality worth noting should add a description of the change to the change log file? For the record, this is _not_ the same as a cvs change log entry in that not every checkin will be reflected in the change log document. The caudium project has a rolling change log that might be worth looking at for inspiration.
Does anyone have any opposition to the idea?
Bill
Hm, I thought I did that already.. :)
/ Mirar
Previous text:
2004-05-06 18:19: Subject: change log
OK, now that 7.7 is open for business, how about a "rule" that developers that add or change functionality worth noting should add a description of the change to the change log file? For the record, this is _not_ the same as a cvs change log entry in that not every checkin will be reflected in the change log document. The caudium project has a rolling change log that might be worth looking at for inspiration.
Does anyone have any opposition to the idea?
Bill
/ Brevbäraren
I'll do my best to stick to that.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-06 18:19: Subject: change log
OK, now that 7.7 is open for business, how about a "rule" that developers that add or change functionality worth noting should add a description of the change to the change log file? For the record, this is _not_ the same as a cvs change log entry in that not every checkin will be reflected in the change log document. The caudium project has a rolling change log that might be worth looking at for inspiration.
Does anyone have any opposition to the idea?
Bill
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
Martin Stjernholm, Roxen IS ＠ Pike developers forum -
Mirar ＠ Pike developers forum