|Re: [cross-project-issues-dev] Component release hiding (was Re: [Brainstorming] Why (not) a "Final Daze" in SimRel?)|
You assume an undue degree of perfection in releng's. Lower
bounds are generally pretty inaccurate, particularly if they
reflect an underlying semantic rather than source incompatibility.
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.
I agree that the current manual Daze activities deserve to be automated, especially the XML mirror properties. One year I had an " typo. No diagnosis. It was a few years before I spotted that size=3 probably needed to increase to size=5 to accommodate the two new properties. Again no diagnosis. I'm lucky that my releng predecessor wrote a shell script to rename RCx ZIPs and recompute their hashes.
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.
ÂÂÂ ÂÂÂ Ed Willink
On 28/06/2017 14:06, Mickael Istria wrote: