| Summary: | [project] P2 repository details | ||
|---|---|---|---|
| Product: | [Modeling] OCL | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | OCL Inbox <mdt-ocl-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.2.0 | ||
| Target Milestone: | RC3 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Ed Willink
(In reply to Ed Willink from comment #0) > The update site has a variety of RC's. Is it possible to lose the RC when > the final release is declared? Or is it necessary to recontribute a very > late no change suffix-less 'RC5'? https://wiki.eclipse.org/OCL/Dev/Releng/Quiet_Week#Prepare_the_downoadable_zips_area explains how to remove the RC. > Is it possible to put a dummy page at each P2 repository location so that > visitors with a browser get an instruction to use Install New Software, > possibly plus a directory tree? At present you get a disconcerting 404. Easy. Just emulate the copy of p2.index for index.html. Pushed to master for RC3. CLOSED after more than a year in the RESOLVED state. |