Re: Preparing for release - Freeze on master

[Koen Kooi <k.kooi@student.utwente.nl>]

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

On 17-11-10 10:56, Graeme Gregory wrote:
> On 17/11/2010 09:12, Koen Kooi wrote:
>> On 16-11-10 19:20, Khem Raj wrote:
>>> Hello All,
>>
>>> In order to get to the 2010.12 release, I would like to request to
>>> stop pushing any changes to master until release. Please keep your
>>> changes in you local tree ready for when the window
>>> opens again after the release.
>>
>> At OEDEM we agreed that the release would pick a tested branch tag to
>> avoid such a draconic freeze.
>>
> I must say I am puzzled why the freeze when git supports branches. In
> the past we have just picked a point branched then cherry picked
> anything interesting that went into org.openemedded.dev until release date.

At OEDEM we decided that the release would be a tag, not branch of .dev.
To make this release easy and unobtrusive the release team would pick a
tag of the tested stuff that they thought is best. So the december
release might actually use a tag from september if that proves to be the
most "stable".

I would think our normal commit policy would cover "dangerous" commits
already, so I object to this draconion freeze proposal.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFM462iMkyGM64RGpERAvkmAJ4glGYefhsTMST+UGbZFHI6pjS2qACgrS9g
AvU3Xy0Y1105HoW1/vLGU2I=
=EVng
-----END PGP SIGNATURE-----