Hi, > > I was a bit surprised to see HISTORY.txt having separate entries for > > log4j 1.2.12-rc1 and rc2 since those builds don't have the > > endorsement of the the project and will never be part of the official > > history of log4j. In the next build, I'd wrap all the chances since > > 1.2.11 into one entry for 1.2.12. > > The plan is to consolidate them before the final release. It might be > useful to know which rc the change was applied. But with the final > release, > none of that will matter, so it will be consolidated.
I'm -0 on consolidating. The HISTORY.txt file doesn't have to correspond to any official release. It's just a convenience for users, a step above having to consult the CVS logs as to see what happened. As such, it might be useful, especially to advanced users, to know exactly which release contained what changes. Furthermore, the convention of associating this information with sub-releases (alpha, beta, rcs, etc.) is fairly common in both big (Weblogic, Eclipse, httpd, etc) and small (Jakarta commons) projects. So if the other committers really want to consolidate all the changes for a given release's candidates into one section, that's fine with me (hence the -0 and not -1), but I think keeping separate is valuable to some people and doesn't do any harm to anyone. Yoav
BEGIN:VCARD VERSION:2.1 N:Shapira;Yoav FN:[EMAIL PROTECTED] ORG:MIT Sloan School of Management TITLE:System Design and Management Fellow URL;WORK:http://www.yoavshapira.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050611T145830Z END:VCARD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
