bzr 1.18rc1 source frozen

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

>> I personally don't feel any need to have an *rc* period for the windows
>> installer. I'm perfectly fine with "release X.YbetaZ-windows1" and then
>> "X.YbetaZ-windows2" if we find problems. The same way we are thinking to
>> do beta releases if there are problems with the bzr code. (step 3).
>> I would really *like* to not have to do a spurious extra build on every
>> release. If past history holds true, I'll be doing them anyway because
>> of bundling issues, but at least they won't be mandated by our release
>> process.
> 
> Right,  builds with no changes but the version number are fairly clearly waste.
> 
> Gary said earlier in this thread that he did want a source freeze to
> give time for Windows installers before the general announcement, but
> that's orthogonal to having an rc.
> 

Right. I think having a "gone gold, go build the installers" is a good
thing.

I think we want Mac and Windows installers to get built within ~1 week's
time of the "gone gold", and then the bzr-announce@ email set once those
are in place.

Actually, I almost got bzr-1.18rc1 built within a day of the tarball,
but then I got hung up waiting for bzrtools 1.18 (not realizing Aaron
was out of town until the end of the day.)

So tomorrow should see 1.18rc1 win32 installers built.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqA6tIACgkQJdeBCYSNAAP3JgCfZpre+5MRkuHGJ930ic4FA6AP
q7gAnRksD6uP7oe7i7D7UyovUGqKDUqW
=wXt6
-----END PGP SIGNATURE-----