On 01/07/2016 06:20 PM, Doug Schaefer wrote:
By the way, some time ago, we discussed the idea of policies about
contributing immutable URLs and fully qualified versions to
Simrel, in order to provide predictability and reproducibility.
Have these ideas been abandoned? If we were to enforce review, we
could put additional checks to verify at least that versions are
fully qualified.
The planning council has made this a requirement for Neon. I'm not
sure how enforceable this is going to be but if everyone follows the
rules, the aggregate build will be reproducible.
Good. I wasn't aware of that. That's a major step forward.
However a quick lookup on b3aggrcon files shows that many (probably the
majority) of contributions seems to ignore that rule; as they either
don't specify a versionRange or specify a versionRange in a
[a.b.c,x.y.z] way.
The SimRel rules are very good, but here is an example of how they get
ignored. My idea with Gerrit is that by enforcing Gerrit reviews, we'll
make it easier to enforce such rules.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
