Bugzilla – Full Text Bug Listing
| Summary: | Top-level download directory for coordinated releases | ||
|---|---|---|---|
| Product: | Community | Reporter: | Bjorn Freeman-Benson <bjorn.freeman-benson> |
| Component: | Cross-Project | Assignee: | Cross-Project issues <cross-project.inbox> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, nboldt |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 153978 | ||
| Bug Blocks: | |||
|
Description
Bjorn Freeman-Benson
I'm moving this to Callisto to get feedback from the cross-project team. The motivation here is that, for Callisto, I needed to explicitly ask our mirrors to fetch the download.eclipse.org/callisto directory, as it was a new top-level directory that was only fetched by mirrors who replicate the entire site. By putting all the cross-project content inside a generic top-level directory, I'll only need to ask mirrors once to update their scripts, not every year. Any suggestions as to the name of the directory would be appreciated. D. I don't have a preference for a name. Just a note, we'll still need separate update sites defined for each coordinated release until bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=123162 is addressed. If the directories are moved to the new common location, please ensure that the update site url defined in our Callisto features http://download.eclipse.org/callisto/releases still resolves to the new filesytem location :-) I don't think we'd "move" callisto under this new top-level directory. But I was thinking of: http://download.eclipse.org/coordinatedreleases/europa http://download.eclipse.org/coordinatedreleases/titon http://download.eclipse.org/coordinatedreleases/pluto etc... need a better name? ------------^^ This is silly... I really need a name for this, and I just don't have any ideas... Help? well, I would say "fullmoon" but that'll get confusing :) and "squirrel" is already taken :) How about just the word "released". Would you, each year, still want to define aliases/redirects to a more human readable name, e.g. http://download.eclipse.org/released/europa --> http://download.eclipse.org/europa or does that not work with mirror's in the mix? Good suggestion :-) You might just want to put "releases" to avoid confusion with people seeing a certain directory, for instance Europa, before it is actually released. (People seem to always assume our releases are available before they actually are :-) You mean like Firefox? http://eclipsewebmaster.blogspot.com/2006/10/firefox-20-released-just-wait-24-hours.html ;-) I was wondering if a final decision has been made on the update site name for Europa. Our M4 is next week and I'd like to include the Europa update site in our features. My understanding is that our first submission to Europa will be M4 - is this correct? http://wiki.eclipse.org/index.php/Europa_Simultaneous_Release#Milestones_and_Release_Candidates So far we have download.eclipse.org/releases/europa Going one, going twice... download.eclipse.org/trains/europa ? releases it is. http://download.eclipse.org/releases/europa has been created. With Callisto we had three update sites, release, interim and staging. http://wiki.eclipse.org/index.php/Callisto_Coordinated_Update_Sites#Central_Callisto_Sites If memory serves me correctly, David used to push the updates for each milestone to the staging update site so everyone could test it. Then once everyone was ready, he would push the updates to the release directory. http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg00167.html How will this be accomodated until the new update site http://download.eclipse.org/releases/europa If we are going to follow the same approach for Europa, shouldn't there be another releases and staging subdirectory like this http://download.eclipse.org/releases/europa/releases and http://download.eclipse.org/releases/europa/staging Or alternatively, you could hide the staging directory somewhere else. (In reply to comment #12) > Or alternatively, you could hide the staging directory somewhere else. > I do recall that by the end of Callisto we purposely did not have the staging area mirrored ... wasn't really needed, and just complicated the "quick test" before rolling it out. So, it should be outside the "easily mirrored" location :) Okay thanks, I'll update our features with the europa update site for M4. . |