Re: [OE-core] Branched for release

2015-10-01 Thread Khem Raj
On Thu, Oct 1, 2015 at 2:16 PM, Richard Purdie wrote: > On Thu, 2015-10-01 at 17:30 -0300, Otavio Salvador wrote: >> I think what Khem means is that any time is time to discuss the >> release process as this is a community driven project and we must to >> be open for feedback and revisit our previ

Re: [OE-core] Branched for release

2015-10-01 Thread Khem Raj
On Thu, Oct 1, 2015 at 1:28 PM, Khem Raj wrote: > On Thu, Oct 1, 2015 at 1:25 PM, Richard Purdie > wrote: >>> 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 cade

Re: [OE-core] Branched for release

2015-10-01 Thread Richard Purdie
On Thu, 2015-10-01 at 17:30 -0300, Otavio Salvador wrote: > I think what Khem means is that any time is time to discuss the > release process as this is a community driven project and we must to > be open for feedback and revisit our previous concepts. There is a time and a place for such discussi

Re: [OE-core] Branched for release

2015-10-01 Thread Otavio Salvador
On Thu, Oct 1, 2015 at 5:25 PM, Richard Purdie wrote: > 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-n

Re: [OE-core] Branched for release

2015-10-01 Thread Khem Raj
On Thu, Oct 1, 2015 at 1:25 PM, Richard Purdie wrote: >> 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

Re: [OE-core] Branched for release

2015-10-01 Thread Richard Purdie
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

Re: [OE-core] Branched for release

2015-10-01 Thread Khem Raj
> On Oct 1, 2015, at 8:37 AM, Richard Purdie > wrote: > > On Thu, 2015-10-01 at 07:28 -0700, Khem Raj wrote: >> On Thu, Oct 1, 2015 at 7:24 AM, Richard Purdie >> wrote: >>> Just a heads up for people that we've branched for release and that >>> jethro branches are now available. Bitbake branch

Re: [OE-core] Branched for release

2015-10-01 Thread Richard Purdie
On Thu, 2015-10-01 at 11:41 -0300, Otavio Salvador wrote: > I agree. > > The mix between codenames and version numbers cause a lot of confusion > for outsiders. We, involved with the project development can handle it > (even though sometimes I ask myself if one codename is older or newer > than an

Re: [OE-core] Branched for release

2015-10-01 Thread Richard Purdie
On Thu, 2015-10-01 at 07:28 -0700, Khem Raj wrote: > On Thu, Oct 1, 2015 at 7:24 AM, Richard Purdie > wrote: > > Just a heads up for people that we've branched for release and that > > jethro branches are now available. Bitbake branched as 1.28, I decided > > to save bitbake 2.0 for another occasi

Re: [OE-core] Branched for release

2015-10-01 Thread Khem Raj
On Thu, Oct 1, 2015 at 8:03 AM, Carlos Alberto Lopez Perez wrote: > On 01/10/15 16:28, Khem Raj wrote: >> I would also suggest to not use codenames in branches >> but rather the numbered release. If we want to use codenames for >> branches then lets drop the numbered release names. >> > > I sugges

Re: [OE-core] Branched for release

2015-10-01 Thread Carlos Alberto Lopez Perez
On 01/10/15 16:28, Khem Raj wrote: > I would also suggest to not use codenames in branches > but rather the numbered release. If we want to use codenames for > branches then lets drop the numbered release names. > I suggest using both (codename+release_number). Ex: jethro-2.0 or 2.0-jethro (pro

Re: [OE-core] Branched for release

2015-10-01 Thread Otavio Salvador
On Thu, Oct 1, 2015 at 11:28 AM, Khem Raj wrote: > On Thu, Oct 1, 2015 at 7:24 AM, Richard Purdie > wrote: >> Just a heads up for people that we've branched for release and that >> jethro branches are now available. Bitbake branched as 1.28, I decided >> to save bitbake 2.0 for another occasion.

Re: [OE-core] Branched for release

2015-10-01 Thread Khem Raj
On Thu, Oct 1, 2015 at 7:24 AM, Richard Purdie wrote: > Just a heads up for people that we've branched for release and that > jethro branches are now available. Bitbake branched as 1.28, I decided > to save bitbake 2.0 for another occasion. what would be the occasion ? this time lets branch consi

[OE-core] Branched for release

2015-10-01 Thread Richard Purdie
Just a heads up for people that we've branched for release and that jethro branches are now available. Bitbake branched as 1.28, I decided to save bitbake 2.0 for another occasion. These branches are going to track master for a while yet as we stabilise the release. Cheers, Richard --