Hi all, (Thomas) > This is fixed in SVN (r765120), it was a silly error.
I seems like this change could have fixed visible errors so, as this didn't go through the usual bug reporting procedure, I'd say this NeedsReleaseNote [1]. ;-) I'm not sure if, before releasing a new version commits are throughly analyzed, though for (potentially) missing things in "CHANGES": I've never got to quite understood if there's a procedure for this -- I've looked at file "MAINTAIN" but nothing relevant was found (nevertheless, step 8 of "Distribution Creation" seems somehow related). Should a similar tip (analyze commits before releasing a new version) be added to the MAINTAIN file? (I'd say it could lead to quite a bit of overhead, so I'd vote for discreetly adding stuff to "CHANGES" whenever relevant, the currently (apparently) used approach, at least in some commits by Cameron.) Regards, Helder [1] https://issues.apache.org/bugzilla/describekeywords.cgi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
