Re: [cdt-dev] Proposed Schedule for 8.3 and 8.4

[Doug Schaefer <dschaefer@xxxxxxx>]

Hmm, great point. I don't think we're doing anything that relies on 4.x
yet so I don't think that's an issue.

On 13-07-30 10:34 AM, "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
wrote:

>
>There is an expectation that CDT Kepler is compatible with Eclipse 3.8 so
>Kepler SR2 should also be compatible with 3.8.
>
>If you want to promote CDT 8.3.1 into the Release train, it would thus
>have to be compatible with Eclipse 3.8 too.
>I'd personally be in favor of that, but I'm not sure if all others on CDT
>are in line ?
> 
>Thanks,
>Martin
>--
>Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River
>direct +43.662.457915.85  fax +43.662.457915.6
>
>
>-----Original Message-----
>From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
>Behalf Of Doug Schaefer
>Sent: Wednesday, July 24, 2013 10:49 PM
>To: CDT General developers list.
>Subject: Re: [cdt-dev] Proposed Schedule for 8.3 and 8.4
>
>I'm leaning that way too. We can do an 8.2.2 in the same time frame, at
>least build and publish it, for those interested. But yeah, I like the
>idea of pushing 8.3.1 to the Kepler SR-2. There doesn't seem to be any
>restriction on that (Egit is pushing new releases every SR, for example).
>
>BTW, no rush. I'm on holidays too from Aug 1-14. So as long as we slowly
>firm up between now and when I get back we'll be ready to go.
>
>On 13-07-24 4:44 PM, "Marc-André Laperle"
><marc-andre.laperle@xxxxxxxxxxxx> wrote:
>
>>On Wed, 24 Jul 2013 16:41:08 -0400
>>Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> wrote:
>>
>>> Hi Doug,
>>> 
>>> Thanks for looking into that. This schedule looks good. For SR2, I
>>> think it would probably be simpler to do a 8.3.1 or else we would
>>> have 3 active branches for a while (assuming we would be doing a
>>> 8.3.1 before June). We could still back port fixes to the 8.2 branch
>>> on demand like we do for older branches right now.
>>
>>> With that in mind,
>>> would it be OK to contribute CDT 8.3.1 to the Kepler release train
>>> for SR2?
>>
>>
>>I mean, from the C/C++ EPP perspective.
>>
>>
>>> Marc-Andre
>>> 
>>> (BTW, I think Marc K will likely want to comment on the schedule but
>>> he's on vacation right now this week and next week, I believe)
>>> 
>>> On Tue, 23 Jul 2013 04:01:15 +0000
>>> Doug Schaefer <dschaefer@xxxxxxx> wrote:
>>> 
>>> > Hey gang,
>>> > 
>>> > To follow up on our plan to switch to 6 month releases, I plotted
>>> > out a possible schedule. These dates are release dates on the
>>> > Friday with the builds from Tues (plus any respins).
>>> > 
>>> > Fri, Aug 23 - CDT 8.2 SR1 RC1
>>> > Fri, Sep 06 - CDT 8.2 SR1 RC2
>>> > Fri, Sep 13 - CDT 8.2 SR1 RC3
>>> > Fri, Sep 20 - CDT 8.2 SR1 RC4
>>> > 
>>> > Fri, Aug 23 - CDT 8.3 M1
>>> > Fri, Sep 27 - CDT 8.3 M2
>>> > Fri, Oct 25 - CDT 8.3 M3
>>> > Fri, Nov 22 - CDT 8.3 RC1
>>> > Fri, Nov 29 - CDT 8.3 RC2
>>> > Fri, Dec 06 - CDT 8.3 RC3
>>> > Fri, Dec 13 - CDT 8.3 RC4
>>> > 
>>> > Also trying not to release just before the holiday week in Dec.
>>> > 
>>> > Kepler SR-1 is in sync with the train.
>>> > 
>>> > The milestones for 8.3 are 4 weeks, as opposed to 6 weeks that are
>>> > traditional with Eclipse. We would put the latest available CDT
>>> > into the train milestone builds (M1-3) with the final 8.3 going into
>>>M4.
>>> > 
>>> > For 8.4, I think we'd probably line up again with the Eclipse train
>>> > milestones with Luna starting with M5.
>>> > 
>>> > What happens for Kepler SR-2 is a good question. It releases at the
>>> > end of Feb with RC's starting Jan 23. We could do 8.3.1 for then on
>>> > a shortened SR schedule. Or do an 8.2.2 with minimal changes.
>>> > Depends on whether we want to step on the gas, or go for stability.
>>> > 
>>> > BTW, Eclipse train schedules here:
>>> > http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan
>>> > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan
>>> > 
>>> > Comments?
>>> > Doug.
>>> 
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>>_______________________________________________
>>cdt-dev mailing list
>>cdt-dev@xxxxxxxxxxx
>>https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev