|Re: [cross-project-issues-dev] Component release hiding (was Re: [Brainstorming] Why (not) a "Final Daze" in SimRel?)|
Before the SimRel, it was difficult to establish a coherent set of plugins for a complex mix of components; e.g. CDT + Sirius.
The SimRel gives a much higher degree of confidence about a compatible set of versions so that users who ensure that they stick to a particular release are probably ok. Note how we have avoided Guava anarchy.
The problem occurs at the transition. Hiding makes the version change atomic. No hiding means that users updating slightly before SimRel can get some hybrid installations that probably haven't been tested and we certainly do not want to debug.
Ditto downloads. It should be possible to register a pattern with the PMI that renders a nice downloads page. It should be possible to instruct the PMI to migrate certain pattern elements to archive so that the downloads page entry points at the archive and the archive has an index that supports use of the archive. With the PMI in charge of the downloads page, the PMI could manage hiding too and update of project repos. Maybe 90% of the activities that require shell access could be eliminated.