Hi
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.
Regards
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
http://download.eclipse.org/modeling/updates/
<http://download.eclipse.org/modeling/updates/> 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".
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev