Honest, I had not seen Sam's question before my latest posting ... guess I could have waited a little longer. But I hope my "pre" response in https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12901.html
answers the question. From: Sam Davis <[email protected]> To: Cross project issues <[email protected]>, Date: 01/08/2016 01:57 PM Subject: Re: [cross-project-issues-dev] Enforce Gerrit for Simrel? Sent by: [email protected] On Fri, Jan 8, 2016 at 8:36 AM, Mickael Istria <[email protected]> wrote: It would be possible, but checking that a repo isn't a composite doesn't validate that its content are immutable. Some repositories contributed have their content growing (cumulative build output) and some others have content overwritten by newer build. If a fully qualified version is not specified, is the requirement that the repository be immutable, or simply that it only contain one version of each feature at a time? In other words, is it ok to update versions by just replacing the content of the repository? It's not clear to me from reading https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Integrate_Early_and_Often In any case, for Mylyn, I am considering updating our build job so that it will push a change to Gerrit to update the qualifiers in our b3aggrcon file. Then all we would need to do after a build runs is approve the change._______________________________________________ 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
_______________________________________________ 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
