From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Commits to master in my absence
Date: Mon, 1 Aug 2011 13:18:07 -0700 [thread overview]
Message-ID: <4E3709FF.4090904@mentor.com> (raw)
In-Reply-To: <1312228607.2344.526.camel@rex>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/01/2011 12:56 PM, Richard Purdie wrote:
> On Mon, 2011-08-01 at 12:25 -0700, Tom Rini wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08/01/2011 06:45 AM, Richard Purdie wrote:
>>
>>> I'm a little frustrated to see what happened when I was away from a
>>> couple of days. I thought we'd agreed we'd queue up patches in a branch
>>> and then I'd take care of things when I got back.
>>
>> So, I agree with everything you did say. But I'd also like to suggest
>> we should have gone with "merge everything Monday" not "merge everything
>> Wednesday before RP runs off". Yes, this would have meant either moving
>> some testing, or having testing also pull from a different (merged)
>> branch. And I too was "wait, what, more stuff went in? I thought we
>> caught the big problem already".
>
> If I'd merged everything unexpectedly and not communicated the situation
> I think that would be bad. As it was, I did merge things but I also
> hopefully clearly communicated the issues and the expectation. Master is
> the development tip and some instability, particularly as new features
> merge is not entirely unexpected at this point in the cycle.
>
> I'd hope we don't end up in a situation like that again, if we do, I'll
> see what other options there and weigh them up as the situation
> dictates.
Yes, it was an intentional and communicated decision. I guess what my
gut says right now is that while some folks are willing to live with
some "it's broken, try again in a few days or go back to ...", a lot of
the community expects things to be mostly working, and there was also
some "ok, I want to expand / use this stuff, but..." that we ran into,
which really is situation dependent. And yes, next time we will need to
weigh the options once again.
- --
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJONwn7AAoJEI4NMjfc3nJx2vQH/2u2MKHdqhsHNfoZoHlhPCJQ
jk144kwp69HHVS9gKjiJCf1fkum9MTblT5V5VDIYgoD2yHDBnCe/P/9GWS8rlTcq
lUweqPMDuWvoWPEGRWnNLPAnXP+bsWqoQLGEUuHkcmMag4yJsJSZYTmU6btTOSNa
ON6Q4RnkTcD08AiHark/R5YHS46HaQ6tVyRpK3DgMUgfGVGnYa0EFzGG73p6q44x
GKsXqNRverf4uu9KbnRTcciuxeIytGlZ3ewT9yHJBcKOjaT9a8FEkA03fHOIqRy/
VJnfjOL4NbdoSRa67INQm8nAnI20WzxCrkzZPJ/2+VXXCfrZ4TFiabUviocPpmA=
=oTtt
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-08-01 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 13:45 Commits to master in my absence Richard Purdie
2011-08-01 17:59 ` Khem Raj
2011-08-01 19:25 ` Tom Rini
2011-08-01 19:56 ` Richard Purdie
2011-08-01 20:18 ` Tom Rini [this message]
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=4E3709FF.4090904@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox