On Fri, 2012-08-10 at 08:59 -0400, Gary Oberbrunner wrote:
> On Fri, Aug 10, 2012 at 8:32 AM, Russel Winder <[email protected]> wrote:
> > Did src/CHANGES.txt get changed for the 2.2.0 release?
> 
> Yes.  src/CHANGES.txt should contain all changes to date.  The release
> header gets added by a script and only checked in on the release
> branch, if that's what you're missing.  That way CHANGES.txt is ready
> for post-2.2.0 work immediately.  See
> http://www.scons.org/wiki/ReleaseHOWTO/SimplifiedReleaseProcedure for
> how the release was produced and please ask questions or suggest
> improvements -- this release workflow is drastically simplified from
> the old days, but because it's brand new I'm sure there are ways to
> improve it.

Hummm... simpler is better :-) The problem here is that src/CHANGES.txt
in default/tip doesn't mention 2.2.0 just 2.x.x and so it is not clear
what to do to add new material post release.

So I think there needs to be a post release amendment to src/CHANGES.txt
in default.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[email protected]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev

Reply via email to