From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: yocto <yocto@yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Feature Completion Deadline for 1.4 looming
Date: Mon, 04 Mar 2013 17:26:42 +0000 [thread overview]
Message-ID: <1362418002.29587.42.camel@ted> (raw)
In-Reply-To: <CAP9ODKozO-vpHdqDWxPMnYaaCt6eZUy_EjoEfAeDObdSjKj2_g@mail.gmail.com>
On Mon, 2013-03-04 at 14:00 -0300, Otavio Salvador wrote:
> On Mon, Mar 4, 2013 at 11:35 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > The 1.4 release is scheduled for 2013/04/26. We have one milestone
> > release before then, M5 on 2013/03/17. This is also the feature complete
> > deadline.
> >
> > This means if there are features or other changes you want to see in
> > 1.4, they need to be in by the 17th[1]. After the 17th we'll be doing
> > bugfixing and stabilisation and new features will have to wait for 1.5.
> >
> > [1] Within reason, large unexpected invasive changes appearing on the
> > 17th will probably not make it unless the solve world hunger or have an
> > equally impressive benefit.
>
> The systemd integration? Will it be reworked so we have an upgrade path?
I'd also mention that systemd is something I know about and is a
priority for this release so I'm going to have some flexibility in
getting it resolved.
The main reason for sending this out is people have wanted more notice
about feature freeze in the past...
Cheers,
Richard
prev parent reply other threads:[~2013-03-04 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 14:35 Feature Completion Deadline for 1.4 looming Richard Purdie
2013-03-04 17:00 ` Otavio Salvador
2013-03-04 17:16 ` Burton, Ross
2013-03-04 17:26 ` Richard Purdie [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=1362418002.29587.42.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox