Hi Cameron,
>> 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). > > For the 1.6 and 1.7 releases, I went through all the commits since the > previous release and updated the CHANGES file. Recently, I have been > making sure to update CHANGES as I go, to avoid having to do that. It > shouldn’t be hard to come up with a list of commits that didn’t touch > CHANGES, and only look at those, so if CHANGES isn’t updated as fixes > are checked in, I guess it’s not a big problem. Yeah, this sounds reasonable (and the filtered commit list a good idea)! ;-) >> Should a similar tip (analyze commits before releasing a new >> version) be added to the MAINTAIN file? > > I just tweaked the wording of step 8 there to say to update CHANGES > before a release. Great. :-) Thanks, Helder --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
