Community
Participate
Working Groups
Stable release update site locations should be listed on the MPC homepage or in the wiki: http://www.eclipse.org/forums/index.php?t=msg&goto=656560&S=353438f3f9deffd9a7dbbfdc7c97bb40
Created attachment 191069 [details] patch Steffen, i created a new download archive page with the important zips and update sites.
Created attachment 191070 [details] mylyn/context/zip
I have applied that patch but I don't see that it's linked anywhere: http://eclipse.org/mpc/archive.php . It should show in the navigation bar on the left and we should also fix the download section on the main page to point to it. I would move that section above the screenshot otherwise it's easy to miss. I would also remove the download zip link from there and replace it by a link that says something along the lines of "Download archive and zip files".
Created attachment 191320 [details] patch It seems you missed the change for index.html in the last patch. Just use the next patch with your suggested modifications. Fixed header on downloads page, switched position of downloads and screenshot section, added Downloads to menus und navbar
Created attachment 191321 [details] mylyn/context/zip
Thanks Benjamin1 I have applied that patch.
Thanks guys. The situation is much more clear for Helios releases. For Indigo, I see "ZIP file: not yet available". Ok, but what adopters really need here are links to milestone builds. A common pattern used by other projects is to preserve milestones on the download server and the page until the release is final. Adopters may be a milestone or two behind, so it's important to not remove the old milestone builds when a new one is available.
Benjamin, once you have committer rights, can you add a listing that points to the corresponding milestone builds and downloads?
Yep, makes sense to put distict links for all the milestones on the website. Will try to squeeze this in for M7.
I have added the release repository for the 1.1.0 release to the website. We'll keep this bug in mind for the next release cycle and will provide stable repositories for each milestone.