From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Branched for release
Date: Thu, 01 Oct 2015 21:25:46 +0100 [thread overview]
Message-ID: <1443731146.14733.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <3712B443-8857-41CB-87F9-DFFC12FE69E9@gmail.com>
On Thu, 2015-10-01 at 10:24 -0700, Khem Raj wrote:
> > If we want to discuss this all again, so be it, but on the eve of
> > release really isn't the time to start it all again.
>
> so when is the right time ? Do we have long enough pre-notice about
> when we the branching is going to happen?
We release approximately in April and October with a six month cadence.
After the complaints about communication, there have been weekly status
updates and the release dates were also *clearly* shown in there for
when the release was planned. Incidentally, if those aren't useful,
Stephen and I can stop doing them.
Its not unreasonable to assume the branch for release happens sometime
before the first rc build of the release.
Cheers,
Richard
next prev parent reply other threads:[~2015-10-01 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 14:24 Branched for release Richard Purdie
2015-10-01 14:28 ` Khem Raj
2015-10-01 14:41 ` Otavio Salvador
2015-10-01 15:42 ` Richard Purdie
2015-10-01 15:03 ` Carlos Alberto Lopez Perez
2015-10-01 15:23 ` Khem Raj
2015-10-01 15:37 ` Richard Purdie
2015-10-01 17:24 ` Khem Raj
2015-10-01 20:25 ` Richard Purdie [this message]
2015-10-01 20:28 ` Khem Raj
2015-10-02 1:37 ` Khem Raj
2015-10-01 20:30 ` Otavio Salvador
2015-10-01 21:16 ` Richard Purdie
2015-10-02 1:46 ` 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=1443731146.14733.30.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.