On Dec 8, 2010, at 10:42 AM, Chris Hostetter wrote: > *** > > ...my vote is to start having CHANGES.txt focus solely on the changes > commited to the branches that lead to that release (so 4.1.1's CHANGES.txt > will list 4.0, 4.1, 4.2, and 4.2.1 - but not 3.1, or 4.1.1) but i could > also be pursuaded that it should only be that exact release (4.1.1 only > contains commits specific to 4.1.1) > > I think that general approach is the only sane thing to do (both from a > developer sanity stand point, and from a clarity to users standpoint > about what versions on what branches contain what bug fixes/features) now > that we are knowingly and deliberately maintaining multiple branches under > active development. >
Makes sense to me. History is easily obtained from other places and people will likely have the context of older changes already. -Grant --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
