Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 03:15:59PM -0700, Andre McCurdy wrote: > On Mon, Mar 18, 2019 at 1:00 PM Adrian Bunk wrote: > > > > On Mon, Mar 18, 2019 at 11:35:05AM -0400, Tom Rini wrote: > > >... > > > I am however asking if the Boost project is an example > > > of something that, based on my own

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 12:34 PM, Khem Raj wrote: > > > On Mon, Mar 18, 2019 at 5:49 AM Richard Purdie > > wrote: > > Since we established the stable branch maintenance guidelines for OE- > Core the world has changed a little. I'd like to propose we update

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 1:00 PM Adrian Bunk wrote: > > On Mon, Mar 18, 2019 at 11:35:05AM -0400, Tom Rini wrote: > >... > > I am however asking if the Boost project is an example > > of something that, based on my own history building boost stuff and > > comments from others, if something where

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 11:35:05AM -0400, Tom Rini wrote: >... > I am however asking if the Boost project is an example > of something that, based on my own history building boost stuff and > comments from others, if something where "project says it's stable" is > not something that is stable

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 5:49 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > Since we established the stable branch maintenance guidelines for OE- > Core the world has changed a little. I'd like to propose we update the > guidelines to reflect this changing world and the current

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 02:01:37PM +, Burton, Ross wrote: > On Mon, 18 Mar 2019 at 12:49, Richard Purdie > wrote: > > My proposal is therefore that where an upstream has a stable release > > mechanism, we should work with that in OE-Core, taking direct stable > > version upgrades. We've been

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 05:04:43PM +0100, Andreas Müller wrote: > On Mon, Mar 18, 2019 at 4:21 PM Richard Purdie > wrote: > > > > On Mon, 2019-03-18 at 15:59 +0100, Martin Jansa wrote: > > > On Mon, Mar 18, 2019 at 12:49:17PM +, Richard Purdie wrote: > > > > Recently this issue came to light

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 03:21:27PM +, Richard Purdie wrote: >... > > There is huge pressure from people to get changes into stable quickly. > I cannot get people to test changes in master for a time period before > requesting backport. There is also huge pressure to accept no changes > that

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 9:05 AM, Martin Jansa wrote: > On Mon, Mar 18, 2019 at 03:21:27PM +, Richard Purdie wrote: >> I think in the recent climate there is a strong case for kernel stable >> series or openssl, requested or not (presumably someone would request >> regardless). The boost change was an

Re: [Openembedded-architecture] Stable releases and version upgrades

I specifically meant letter releases, which are the true ‘point’ releases in OpenSSL. (E.g. 1.1.1a -> 1.1.1b) Alex > On 18 Mar 2019, at 17.03, akuster808 wrote: > > > >> On 3/18/19 8:49 AM, Alexander Kanavin wrote: >> If you do package version upgrades regularly in master, I’d say that you

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 11:05 AM, Martin Jansa wrote: > Are there (m)any people complaining that stable branches doesn't get > enough bugfix updates (not counting those requesting the actual > backport, because they see the bug in their product)? On the commercial side, I am starting to hear rumblings of

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 11:03 AM, akuster808 wrote: > > > On 3/18/19 8:49 AM, Alexander Kanavin wrote: >> If you do package version upgrades regularly in master, I’d say that you >> eventually learn about whether stable releases can be trusted. I wouldn’t >> need to do any research to say that boost

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 03:21:27PM +, Richard Purdie wrote: > I think in the recent climate there is a strong case for kernel stable > series or openssl, requested or not (presumably someone would request > regardless). The boost change was an exception rather than the rule and > to me its a

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 10:39 AM, Tom Rini wrote: > On Mon, Mar 18, 2019 at 03:32:17PM +, Richard Purdie wrote: >> On Mon, 2019-03-18 at 10:46 -0400, Tom Rini wrote: > Agreed on all parts. > > What I was hoping to ask / discuss is, should we go with "assume > upstream stable branch works for us unless

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 11:46 AM Tom Rini wrote: > On Mon, Mar 18, 2019 at 02:01:37PM +, Burton, Ross wrote: > > On Mon, 18 Mar 2019 at 12:49, Richard Purdie > > wrote: > > > My proposal is therefore that where an upstream has a stable release > > > mechanism, we should work with that in

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 8:49 AM, Alexander Kanavin wrote: > If you do package version upgrades regularly in master, I’d say that you > eventually learn about whether stable releases can be trusted. I wouldn’t > need to do any research to say that boost shouldn’t be touched but OpenSSL is > fine, and can

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 10:34 AM, Andreas Müller wrote: > On Mon, Mar 18, 2019 at 1:49 PM Richard Purdie > wrote: >> >> Since we established the stable branch maintenance guidelines for OE- >> Core the world has changed a little. I'd like to propose we update the >> guidelines to reflect this changing world

Re: [Openembedded-architecture] Stable releases and version upgrades

If you do package version upgrades regularly in master, I’d say that you eventually learn about whether stable releases can be trusted. I wouldn’t need to do any research to say that boost shouldn’t be touched but OpenSSL is fine, and can similarly split the rest of what I maintain. Alex > On

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 03:32:17PM +, Richard Purdie wrote: > On Mon, 2019-03-18 at 10:46 -0400, Tom Rini wrote: > > On Mon, Mar 18, 2019 at 02:01:37PM +, Burton, Ross wrote: > > > I don't really have a strong opinion on the mechanics behind > > > documenting the behaviour, but how do we

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, 2019-03-18 at 10:26 -0500, Mark Hatle wrote: > Let me start out with, I'm not against this proposal. > > But, I want to mention the cases in my experience where people get > upset with version numbers changing. > > 1) "Regulated devices". For some reason there are a class of devices >

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 1:49 PM Richard Purdie wrote: > > Since we established the stable branch maintenance guidelines for OE- > Core the world has changed a little. I'd like to propose we update the > guidelines to reflect this changing world and the current best > practises. > > Partly this

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, 2019-03-18 at 10:46 -0400, Tom Rini wrote: > On Mon, Mar 18, 2019 at 02:01:37PM +, Burton, Ross wrote: > > I don't really have a strong opinion on the mechanics behind > > documenting the behaviour, but how do we decide what upstreams have > > a > > suitable stable release? We don't

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 7:46 AM, Tom Rini wrote: > On Mon, Mar 18, 2019 at 02:01:37PM +, Burton, Ross wrote: >> On Mon, 18 Mar 2019 at 12:49, Richard Purdie >> wrote: >>> My proposal is therefore that where an upstream has a stable release >>> mechanism, we should work with that in OE-Core, taking

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 7:49 AM, Richard Purdie wrote: > Since we established the stable branch maintenance guidelines for OE- > Core the world has changed a little. I'd like to propose we update the > guidelines to reflect this changing world and the current best > practises. > > Partly this change has been

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, 2019-03-18 at 15:59 +0100, Martin Jansa wrote: > On Mon, Mar 18, 2019 at 12:49:17PM +, Richard Purdie wrote: > > Recently this issue came to light around some lttng* version > > upgrades. > > I do think that particular upstream is in keeping with what we'd > > need/want from a stable

Re: [Openembedded-architecture] Stable releases and version upgrades

On 3/18/19 7:01 AM, Burton, Ross wrote: > On Mon, 18 Mar 2019 at 12:49, Richard Purdie > wrote: >> My proposal is therefore that where an upstream has a stable release >> mechanism, we should work with that in OE-Core, taking direct stable >> version upgrades. We've been doing this already for

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 12:49:17PM +, Richard Purdie wrote: > Recently this issue came to light around some lttng* version upgrades. > I do think that particular upstream is in keeping with what we'd > need/want from a stable branch. There is also quite a bit of discussion related to recent

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, 2019-03-18 at 10:30 -0400, Jonathan Rajotte-Julien wrote: > Note I did not cc the mailing list since > I think it is moving the discussion away from the main focus. It did make the list and FWIW I think it is important to ensure people understand why we're dropping certain patches or

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, Mar 18, 2019 at 02:01:37PM +, Burton, Ross wrote: > On Mon, 18 Mar 2019 at 12:49, Richard Purdie > wrote: > > My proposal is therefore that where an upstream has a stable release > > mechanism, we should work with that in OE-Core, taking direct stable > > version upgrades. We've been

Re: [Openembedded-architecture] Stable releases and version upgrades

On Mon, 2019-03-18 at 14:01 +, Burton, Ross wrote: > On Mon, 18 Mar 2019 at 12:49, Richard Purdie > wrote: > > My proposal is therefore that where an upstream has a stable > > release > > mechanism, we should work with that in OE-Core, taking direct > > stable > > version upgrades. We've been

[Openembedded-architecture] Stable releases and version upgrades

Since we established the stable branch maintenance guidelines for OE- Core the world has changed a little. I'd like to propose we update the guidelines to reflect this changing world and the current best practises. Partly this change has been influenced by a discussion I was part of where GregKH