From: Daiane Angolini <daiane.angolini@freescale.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: review / comments / merge protocol
Date: Thu, 11 Apr 2013 10:33:01 -0300 [thread overview]
Message-ID: <5166BB8D.8010404@freescale.com> (raw)
It was not the first time that one merge was considered "too fast", and
that other one was considered "too slow".
In fact, we do not have a protocol, so, it was not "too fast" or "too
slow".
I know protocol may be boring. But, I believe some formalism can avoid
misunderstood.
One week after meta-fsl-arm dylan announcement I will sent a protocol
proposal. And I will give 2 weeks for voting and discussion. I believe
we need at least 10 participants in the discussion for the protocol aproval.
(do we have 10 active members in the ML?)
If you disagree we need a protocol, it's time to say it. With no
protocol, nothing can be considered "too slow" or "too fast" because
there is no way to measure it.
If you have any protocol idea, please, let me know. I will study the
review/merge protocol used in kernel, u-boot and yoctoproject, and adapt
it to our "reality". But if you have an "easier" protocol, it's time to
say it.
Regards,
--
Daiane
next reply other threads:[~2013-04-11 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 13:33 Daiane Angolini [this message]
2013-04-11 20:14 ` review / comments / merge protocol Eric Bénard
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=5166BB8D.8010404@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.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.