| Summary: | please publish release and milestone builds as p2 repos | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Rafael Chaves <eclipse> |
| Component: | Releng | Assignee: | John Arthorne <john.arthorne> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | simon_kaegi |
| Version: | unspecified | ||
| Target Milestone: | 0.5 RC3 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Rafael Chaves
Raising severity to major as this prevents us from building on top of Orion (it is really a blocker). I'll see if I can do this in our promotion script when we promote our next milestone. If we do this, I picture just having the following: http://download.eclipse.org/orion/updates/integration http://download.eclipse.org/orion/updates/milestones http://download.eclipse.org/orion/updates/releases Where integration and milestones would always contain the builds for the current release cycle. That'd be awesome, thanks. For now, I am making do by running two separate Eclipse applications side-by-side. Too swamped with Platform release this week. I have created a releases repository. I have opened bug 383336 to rename our daily build repository so that we end up with: http://download.eclipse.org/orion/updates/integration http://download.eclipse.org/orion/updates/releases Added some documentation here: http://wiki.eclipse.org/Orion/Repositories |