From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] connman: update to 1.36
Date: Wed, 31 Oct 2018 21:39:37 +0000 [thread overview]
Message-ID: <a7ddb9edd7b0256003aab8b4e2101dbbb90b2bbf.camel@linuxfoundation.org> (raw)
In-Reply-To: <d3099fd6-6334-a61c-7a98-38a381661d90@gmail.com>
On Wed, 2018-10-31 at 13:51 -0700, akuster808 wrote:
> On 10/31/18 12:15 PM, Alexander Kanavin wrote:
> > There is a feature freeze up until thud is released. Generally
> > version upgrades aren’t accepted in M4 phase.
>
>
> Did I miss the announcement that no patches will be accepted?
Nobody has said "no patches will be accepted". The weekly status
reports do have a theme though:
https://lists.yoctoproject.org/pipermail/yocto/2018-September/042436.html
"We’re now into M3 feature freeze so new feature patches, particularly
for unplanned changes will be much less likely to be merged until 2.7
now."
https://lists.yoctoproject.org/pipermail/yocto/2018-October/042725.html
"We’re now past feature freeze and all major changes planned for 2.6
have been merged so only bug fixes will be accepted now."
https://lists.yoctoproject.org/pipermail/yocto/2018-October/042790.html
"We’re now past feature freeze and all major changes planned for 2.6
have been merged so only bug fixes will be accepted now."
https://lists.yoctoproject.org/pipermail/yocto/2018-October/042948.html
We have branched for thud at this point and the new release branches
have been created. We have not started working on master patches yet
though, we’re still concentrating on the 2.6 release.
https://lists.yoctoproject.org/pipermail/yocto/2018-October/043068.html
We’re starting to see patches being submitted for master but these will
continue to be a secondary priority until 2.6 is released.
So I think its quite clear we're focused on 2.6 and whilst the status
update does not spell it out, the definition of M4 is no version
upgrades unless they're for security issues or major bugfixes and no
new features.
Cheers,
Richard
prev parent reply other threads:[~2018-10-31 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 21:05 [PATCH v2] connman: update to 1.36 Oleksandr Kravchuk
2018-10-31 18:59 ` Oleksandr Kravchuk
2018-10-31 19:15 ` Alexander Kanavin
2018-10-31 20:51 ` akuster808
2018-10-31 21:39 ` 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=a7ddb9edd7b0256003aab8b4e2101dbbb90b2bbf.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=open.source@oleksandr-kravchuk.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