From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Preparing for release - Freeze on master
Date: Fri, 19 Nov 2010 11:29:11 +0100 [thread overview]
Message-ID: <ic5jhn$iu7$1@dough.gmane.org> (raw)
In-Reply-To: <1290074903.3183.202.camel@mill.internal.reciva.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 18-11-10 11:08, Phil Blundell wrote:
> On Wed, 2010-11-17 at 11:26 -0800, Khem Raj wrote:
>> Should we create a release branch before we release and solidify that ?
>
> Yes, please do that. We discussed this issue at yesterday's TSC meeting
> (full minutes to follow shortly) and the consensus was that trying to
> enforce a complete freeze on master at short notice is not going to be
> practical.
>
> Obviously the exact process you use is up to you, but I would suggest
> something along the lines of:
>
> 1. make a stabilisation branch from some semi-arbitrary point, maybe one
> of the existing weekly test versions.
At OEDEM we decided that there would be no branch, only a tag, could the
TSC elaborate why they are going against that?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFM5lF3MkyGM64RGpERAr/pAJwIE46snPNsW42xpR6J3wKJGxpw0gCgkvhZ
MFR65AifpMR/v69fhN6JwNQ=
=aCtY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-11-19 10:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 18:20 Preparing for release - Freeze on master Khem Raj
2010-11-16 22:39 ` Paul Menzel
2010-11-16 22:46 ` Khem Raj
2010-11-16 22:52 ` Frans Meulenbroeks
2010-11-16 23:00 ` Khem Raj
2010-11-17 7:16 ` Frans Meulenbroeks
2010-11-17 9:12 ` Koen Kooi
2010-11-17 9:56 ` Graeme Gregory
2010-11-17 10:25 ` Koen Kooi
2010-11-17 19:26 ` Khem Raj
2010-11-18 10:08 ` Phil Blundell
2010-11-18 11:01 ` Graham Gower
2010-11-18 11:31 ` Phil Blundell
2010-11-18 17:18 ` Philip Balister
2010-11-18 11:09 ` Frans Meulenbroeks
2010-11-18 14:07 ` Chris Larson
2010-11-18 16:32 ` Khem Raj
2010-11-19 10:29 ` Koen Kooi [this message]
2010-11-17 19:20 ` Khem Raj
2010-11-17 19:15 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ic5jhn$iu7$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.