On Wednesday, October 22, 2003, at 02:30 PM, Stas Bekman wrote:
Seconded. We try to keep the Changes files to containing only information about changes that help users decide whether they need to upgrade to that newer version or not. If we log everything, the file will become useless. We could just run cvs2lg to autogenerated a list of all cvs changes.
Another important thing I forgot to mention is that when user upgrades to the latest version and suddenly his stuff doesn't work as before, they will probably first go to the Changes file and try to deduct what change could have affected their case. Reading through 10 significact logs will help a user to find that change, but she will most likely give up trying to wade through hundreds of logs to find the relevant change.
Well, that's a little different, and obviously quite useless.
I try to track all changes in my Changes files because I think of it as a list of changes, not only those changes that are significant to those considering upgrading. And for the most part, they don't generally make it harder to evaluate.
It'd be very inconsistent if we log all changes from contributions, but only selected ones from the core developers. And we do a lot of changes, most are of very little interest to an end user.
There is another issue with acknowledging the contributions, but it's probably not the reason to log those contributions in Changes. Perhaps we need to start CONTRIBUTORS and simply list the names of contributors there. We do change docs all the time, and trying to track those changes is not simple and certainly doesn't belong to the current Changes. Suggestions on how to improve that are certainly welcome.
CONTRIBUTORS is okay with me.
Cool. We shell have it then.
BTW, I did acknowledge that I've committed your patch, David, in reply to your email with the patch.
Yeah, I wasn't worried about that. I was just pointing out that if it was supposed to be a comprehensive list of changes, well, it wasn't. But if you guys prefer a different approach, well then never mind. :-)
We just try to walk the thin rope of balance and use our common sense to decide what should be noted and what note, often times noting to each other when we think that some change log is due or on the opposite useless.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
