| Re: [cdt-dev] Proposed Schedule for 8.3 and 8.4 |
Hi,
Sorry for the delay, I was on vacation.
I think the effort of making CDT features more quickly available is a great thing!
To summarize the latest proposal, I believe we were talking about the pattern:
Kepler - June 2013 => CDT 8.2
Kepler-SR1 - September => CDT 8.2.1
ADDED - Off-train - December => CDT 8.3 (minor version increment only) (no C/C++ EPP Package)
Kepler-SR2 - February => CDT 8.3.1 (and a CDT 8.2.2 build)
Luna - June 2014 => CDT 8.4
Although a great improvement, I have a couple of concerns about this schedule:
- it adds an extra release date to our community, which seems to add complexity
- it is not aligned with the Eclipse schedule
- it is not as well aligned with other projects releases
Maybe we can simplify things and follow the SR schedule.
Very simply:
Kepler - June 2013 => CDT 8.2
Kepler-SR1 - September => CDT 8.3 (and a CDT 8.2.1 build)
Kepler-SR2 - February => CDT 8.4 (and a CDT 8.2.2 build)
Luna - June 2014 => CDT 8.5
- This puts our users of CDT in the forefront. The C/C++ EPP Packages would provide new
CDT features to our users every ~4 months.
- Vendors that adopt CDT still get access to the SR builds as before with no new features.
Those vendors don't use the C/C++ Package anyway.
- The schedule follows the Eclipse one, and the one of many other projects
which take this same proposed approach. I believe Orion, Linux Tools, Egit, Mylyn,
all release features at the SR schedule.
Note that in the example above, there would be no maintenance builds for 8.3 and 8.4.
I think that is fine since all bug fixes of those builds will be part of the next
CDT anyway, e.g., fixes for 8.3 will be part of 8.4.
SR builds (8.3 and 8.4) must be minor releases (backwards-compatible) so that
we don't break any projects dependent on CDT (same situation as for a December release).
We will need to be careful about that.
Major releases would only be allowed for the June release.
This means that if someone wants to break the API, they will need to do it on
a separate branch, until master is passed the SR2 release.
New features are not required :) There may be some releases that don't have new
features and simply become a normal maintenance release as before.
Bottom line is that we go 'agile': we follow the eclipse trains and choose
if we want to add features or not for each release. It seems to work well
for other projects.
What do you all think?
Marc
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> Sent: Tuesday, July 30, 2013 11:10 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Proposed Schedule for 8.3 and 8.4
>
> BTW, any other comments on the proposed schedule before we make it the
> plan of record?
>
> Doug.
>
> On 13-07-30 10:59 AM, "Doug Schaefer" <dschaefer@xxxxxxx> wrote:
>
> >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
> >
> >_______________________________________________
> >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