From: James S. <jst...@us...> - 2004-08-31 21:35:36
|
Hi Stephen, On Tuesday 31 Aug 2004 21:37, Stephen torri wrote: > Given how we use ChangeLog at > present I have to hunt down which files may have been affected by a > particular change. I have no guarantee unless I am intimately familiar > with the fix. No, one can simply look at the archive for xine-cvslog. > If I am a user considering getting involved with development and I don't > have any CVS access then I am sunk. You could argue that a prospective developer without CVS access is sunk anyway... Besides, there is the web based cvs viewer which is actually very useful for following changes. > So I think a file that maintains the overall changes of the release > should be maintained. Perhaps we can make the NEWS file contain that? > While the intimate details might be considered a burdensome effort I > consider it a helpful aide. I think maintaining such a file will indeed be a significant burden. I for one have very little time for hacking xine these days, I'd get essentially get nothing done if I had to document every little change. > I have a harder time looking at the code to help determine if > a value used for a const integer was wrong. It might need be 8 instead > of the 9 cause by late night programming So you want this "super changelog" to document any constant values used in the code too?! Just my 2 euro-cent-pennies, James. |