Update of poky to morty branch

Zeeshan Ali zeeshan.ali at pelagicore.com
Thu Jan 12 05:25:01 EST 2017


Hi Gunnar,

On 12 January 2017 at 01:55, Andersson, Gunnar
<gunnar.x.andersson at volvocars.com> wrote:
> Sorry for top-post (terrible webmail editor)
>
>
> That makes sense to me Zeeshan.  Don't put any effort into maintaining GDP 9
> and revisit decision at GDP 12 release.  IMHO.

Good then it probably is a good idea. :)

> ________________________________
> Från: genivi-projects <genivi-projects-bounces at lists.genivi.org> för Zeeshan
> Ali <zeeshan.ali at pelagicore.com>
> Skickat: den 11 januari 2017 14:50:36
> Till: Stephen Lawrence
> Kopia: Genivi Project
> Ämne: Re: Update of poky to morty branch
>
> Hi Stephen,
>
> On 10 January 2017 at 20:22, Stephen Lawrence
> <stephen.lawrence at renesas.com> wrote:
>> Hi,
>>
>>> -----Original Message-----
>>> From: Zeeshan Ali [mailto:zeeshan.ali at pelagicore.com]
>>> Sent: 09 January 2017 12:34
>>> To: Stephen Lawrence <stephen.lawrence at renesas.com>
>>> Cc: Genivi Project <genivi-projects at lists.genivi.org>
>>> Subject: Re: Update of poky to morty branch
>>>
>>> Hi Stephen,
>>>
>>> On 6 January 2017 at 21:23, Stephen Lawrence
>>> <stephen.lawrence at renesas.com> wrote:
>>> > Hi,
>>> >
>>> >> -----Original Message-----
>>> >> From: genivi-projects
>>> >> [mailto:genivi-projects-bounces at lists.genivi.org]
>>> On
>>> >> Behalf Of Zeeshan Ali
>>> >> Sent: 04 January 2017 11:53
>>> >> To: Agustin Benito Bethencourt <agustin.benito at codethink.co.uk>
>>> >> Cc: Genivi Project <genivi-projects at lists.genivi.org>
>>> >> Subject: Re: Update of poky to morty branch
>>> >
>>> > [snip]
>>> >
>>> >>
>>> >> > What is the maintenance cycle for GDP 11? What kind of updates, if
>>> >> > any,
>>> >> can
>>> >> > we expect?
>>> >>
>>> >> My suggestion would be that GDP 11 is maintained until GDP 12 is out
>>> >> but not after. No updates of any kind will get in, only fixes.
>>> >>
>>> >
>>> > I can see that there is a balance to be struck and major new work would
>>> > likely be targeted for the newer version, but I would argue for a
>>> > longer
>>> period.
>>> > Probably a year.
>>>
>>> I'm fine with 1 year support cycle but at the same time supporting 3
>>> versions at the same time could become a lot of extra work for GDP
>>> team. If we are going for 1 year support for each release, I recommend
>>> then we also do 1 release every year.
>>
>> I was thinking more of 2 versions. So GDP 11 would accept updates,
>> whilst GDP 12 was being developed and initially released. Then GDP 11
>> would close to non-fixes with the move to the GDP 13 cycle.
>
> Ah OK so you'd like last two (stable) release branches to be
> maintained? While this might work, I'd like to be conservative here.
> So if the decision is up to me, I'd want to only maintain last release
> (even if that means just reviewing fixes) and master.
>
> The reason is that I (and Viktor) am still new to GDP and GDP 11 has
> already been a learning curve and following your proposal would mean
> that we'll also need to learn and test GDP9, which we have no idea
> about to be able to properly evaluate/review any fixes submitted for
> it. So maybe once GDP 12 is out, we can think about maintaining last
> two releases, rather than only the last one?
>
> --
> Regards
>
> Zeeshan Ali
> _______________________________________________
> genivi-projects mailing list
> genivi-projects at lists.genivi.org
> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects



-- 
Regards

Zeeshan Ali



More information about the genivi-projects mailing list