From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: release-2010.12 branch ready for testing
Date: Fri, 19 Nov 2010 06:46:09 -0700 [thread overview]
Message-ID: <4CE67FA1.6020901@mentor.com> (raw)
In-Reply-To: <ic5jrc$ksc$1@dough.gmane.org>
On 11/19/2010 03:34 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 18-11-10 22:27, Khem Raj wrote:
>> Hello all,
>>
>> The work branch for upcoming 2010.12 release has been created.
>
> Why was this created? We were *very* clear at OEDEM that there would be
> no branch, only a tag.
>
> Why was this changed? I only see some vague handwaving from the TSC
> (well, from Phil, saying it was the TSC) who didn't consult the OE
> developers at all.
>
> The whole point of releases was that they are based of a tag from .dev,
> not some random branch. Again, why was that changed?
At least for making a release tag exist, if we can't have a freeze on
.dev (or otherwise an agreement that .dev should focus on making the
testing packages build and work, over new work) making a temporary
branch to cherry-pick into seems to be the next possible solution.
Otherwise the release tag is just another testing tag...
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-11-19 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 21:27 release-2010.12 branch ready for testing Khem Raj
2010-11-19 8:38 ` Frans Meulenbroeks
2010-11-19 10:34 ` Koen Kooi
2010-11-19 13:46 ` Tom Rini [this message]
2010-11-19 14:16 ` Koen Kooi
2010-11-19 14:44 ` Martin Jansa
2010-11-19 17:34 ` Philip Balister
2010-11-21 2:48 ` Khem Raj
2010-11-19 18:21 ` 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=4CE67FA1.6020901@mentor.com \
--to=tom_rini@mentor.com \
--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.