The download page is driven by the output of the EPP project which builds the packages from the release train repo. A lot of this is automated so I would suggest any change to the release cycle will also need to include how we update this workflow.
Ian From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Doug Schaefer Sent: July-16-13 11:07 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] 6 month release cycle +1 We're going to run into this with CDT. We will want to update the package every 6 months as well. From: Greg Watson <g.wat...@computer.org <mailto:g.wat...@computer.org> > Reply-To: Cross project issues <cross-project-issues-dev@eclipse.org <mailto:cross-project-issues-dev@eclipse.org> > Date: Tuesday, 16 July, 2013 4:13 PM To: Cross project issues <cross-project-issues-dev@eclipse.org <mailto:cross-project-issues-dev@eclipse.org> > Subject: Re: [cross-project-issues-dev] 6 month release cycle While I support more frequent release cycles (PTP release more frequently so it would suit us well), I'd like to also suggest that projects also have more control over the packages available on the download site. In particular, we'd like to be able to update our package with a new build when we bring out a bug fix release so that new users don't need to update the package as soon as they download it. If you're interested in discussing this more, I've opened bug 412864 on this issue. Greg On Jul 2, 2013, at 3:30 PM, Doug Schaefer <dschae...@qnx.com <mailto:dschae...@qnx.com> > 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 <mailto: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
