From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: yocto <yocto@yoctoproject.org>
Subject: 1.7 release feature freeze deadline this Friday
Date: Thu, 28 Aug 2014 08:16:46 +0100 [thread overview]
Message-ID: <1409210206.29296.129.camel@ted> (raw)
If you've been in the various calls or read the minutes you'd know about
this but it was mentioned to me that it has not been highlighted on the
mailing list.
The M3 milestone close is the end of the week and this marks the feature
freeze point for the 1.7 release. We do have M4 after this but that is a
bug fixing and stabilisation milestone.
There are some things I may still consider into M4, particular if
they're related to the stated objectives of the release, specifically
the developer workflow enhancements which is running behind schedule. As
time progresses, it will be increasingly unlikely things of that nature
will merge though.
So if there are things you are after to see in 1.7 time is running out,
I at least need to be aware of them ASAP.
Cheers,
Richard
next reply other threads:[~2014-08-28 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 7:16 Richard Purdie [this message]
2014-08-28 7:18 ` 1.7 release feature freeze deadline this Friday Carlos Rafael Giani
2014-08-28 14:23 ` Richard Purdie
2014-08-28 14:33 ` Gary Thomas
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=1409210206.29296.129.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--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