Spurring on the development of new features is part of what's driving this. Only the early adopters ever download milestone builds and we're trying to be more agile to a larger audience by going twice as often.
D On 13-07-02 4:17 PM, "Igor Fedorenko" <ifedore...@sonatype.com> wrote: >What's the point of releasing often if there are no new features? > >-- >Regards, >Igor > >On 2013-07-02 11:56 PM, Doug Schaefer wrote: >> Funny, that came up in our conversation too. Years ago, M releases were >>awesome. They always had new features and the quality was pretty good. >>But then the quality stopped being so good and there were less features, >>so people cared less about M releases. And that has left a long period >>of time where people really care about Eclipse releases. >> >> D >> >> ________________________________________ >> From: cross-project-issues-dev-boun...@eclipse.org >>[cross-project-issues-dev-boun...@eclipse.org] on behalf of Igor >>Fedorenko [ifedore...@sonatype.com] >> Sent: Tuesday, July 02, 2013 3:49 PM >> To: cross-project-issues-dev@eclipse.org >> Subject: Re: [cross-project-issues-dev] 6 month release cycle >> >> I agree, one year is way too long. I am not even sure 6 months is often >> enough. We had three m2e releases between Juno and Kepler, and I >> consider m2e mature, (relatively) low-activity project. At the same >> time, I never use R builds myself, I always use M-builds as primary >> development environment for my $DAY_JOB. I don't suggest we do >> full-blown release every 6 weeks, but maybe there is a way to elevate >> perceived status of M builds such that users are more comfortable using >> them. >> >> -- >> Regards, >> Igor >> >> On 2013-07-02 11:30 PM, Doug Schaefer wrote: >>> Hey gang, >>> >>> We have a discussion going in the CDT community and we are currently >>> planning out how to achieve a 6 month release cycle. The feeling is >>>that >>> we need to get new features out faster to our users. The year long wait >>> we currently have is making releases sluggish and I fear it's slowing >>> down growth in our community. A 6 month cycle should infuse us with a >>> little more energy, so goes the hope. >>> >>> I mentioned CDT's plans on twitter and a number of senior members of >>>our >>> larger Eclipse community thought it might be a good idea for other >>> projects at Eclipse and maybe for the train itself. And I think so too. >>> >>> Instead of continuing that discussion on twitter, which is fun and >>> everything, I thought we should bring that to a greater audience and >>>see >>> what other projects thought and whether it's something we should bring >>> to the Planning Council and the rest of the EMO. >>> >>> I know there are a number of projects already releasing off stream >>> during the year, but bringing things together more often might be a >>>help >>> to many others. But I'd like to hear your thoughts on that. >>> >>> Doug. >>> >>> >>> _______________________________________________ >>> cross-project-issues-dev mailing list >>> cross-project-issues-dev@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> >_______________________________________________ >cross-project-issues-dev mailing list >cross-project-issues-dev@eclipse.org >https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
