Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Component release hiding (was Re: [Brainstorming] Why (not) a "Final Daze" in SimRel?)


My understanding of the hidden policy is that no SimRel artefact is visible until all SimRel artefacts are made visible concurrently by the webmaster. This makes it hard for users to accidentally upgrade one component without updating another.

Once the release announcement is made, there is a lag before unhiding occurs as a result of action by diverse relengs. You might therefore find that B has been unhidden although A remains hidden. However this doesn't really matter since the project-hidden A is already available via the SimRel repo. If you want to gather a complete collection of download ZIPs you may need to wait a day or two, maybe even raising a Bugzilla or two.

If projects do not hide their releases, it can be easy to accidentally upgrade one component without updating another.


        Ed Willink

On 28/06/2017 13:42, Mickael Istria wrote:
Thanks for the details.
But I still don't get how "hidden" repositories make a difference there. In the best case, they delay the visibility of the issue by a few days, but I'm not sure delaying issues visibility is a good practice.

> NB. In the past many projects offered their own update sites that were often visible in a huge composite such as so that much more than official SimRel repos were on offer. I'm pleased to see that this repo seems to be missing from my current Oxygen workspaces.

Cool, but this is not really the responsibility of SimRel, hence why I suggest to drop this requirement from SimRel "Final Daze".


Back to the top