Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Proposal to move to 6 month release cycle
I include that in the bigger problem of the Simultaneous Release doesn't get updated mid-year. :)

But, yes, the idea is to get features out to our users and adopters faster. Updating the IDE package makes a lot of sense.


From: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
Organization: Eclipse Foundation
Reply-To: "mike.milinkovich@xxxxxxxxxxx" <mike.milinkovich@xxxxxxxxxxx>, "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Tuesday, 2 July, 2013 12:55 PM
To: "'CDT General developers list.'" <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Proposal to move to 6 month release cycle

Seems like goodness IMO.

 

The one thing that is a potential issue is that the “Eclipse IDE for C/C++ Developers” package would not get updated mid-year. I am not sure if there is an obvious solution, but you may want to look into that.

 

Mike Milinkovich

mike.milinkovich@xxxxxxxxxxx

+1.613.220.3223

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: July-02-13 12:29 PM
To: CDT General developers list.
Subject: [cdt-dev] Proposal to move to 6 month release cycle

 

Hey gang,

 

We talked about this on our call this morning. There is a lot of interest, and actually always has been, in moving to more frequent release cycle. Yearly is great if you are a stable platform that doesn't need to change much, but our feeling is that the CDT still has a lot of work left to do.

 

And I actually think that yearly cycles reduces the appeal of contributing to Eclipse. Who wants to make a contribution and then wait a year to have a release they can use it with. Even the major Linux distros release bi-yearly. But let's focus now on the CDT and maybe we can lead by example and join other projects that are already doing this.

 

So here's what we came up with and we need to hear from you and tweak it so that it's captures all our needs (or as many as we can).

  • Release in June along with the Eclipse release train as before.
  • Release the SR-1 for that release in Sept as before.
  • Release a new feature release in December, not too late where it interferes with the holiday season.
  • Release the SR-2 for the June release with the rest of the train in Feb as before to satisfy the needs of people stuck on the older CDT release.
  • Release the SR-1 for the December release in March or April.
  • Release in June again, and repeat.

So, for example, this year we have:

 

June – 8.2.0

Sept – 8.2.1

Dec – 8.3.0

Feb – 8.2.2

Mar – 8.3.1

June – 8.4.0

 

Anyway, before we decide to do this, we need to hear from everyone in the community. Please let us know what you think or if you have any questions (and there should be lots of questions).

 

Thanks,

Doug

Back to the top