The only way to be safe is to re-run the aggregation build after the roll-back, regardless of whether the rollback is to 2.1 or 2.2. That will flush out any issues with dependency. Then, of course, we need a contingency for what happens if aggregation fails (there is a dependency).
In some ways substituting 2.3.1 is easier and safer. > like at least for the EPP packages we should be fine. We need to ensure that the entire release repository is unaffected by the rollback, not just the portions used for EPP. - Konstantin From: [email protected] [mailto:[email protected]] On Behalf Of John Arthorne Sent: Friday, February 22, 2013 1:44 PM To: Cross project issues Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay one week, Friday 3/1 Since the new version of EGit was only introduced in RC3, that could only happen if someone changed their minimum dependency on EGit in their RC4 contribution. That seems unlikely but projects should speak up if they have that constraint. Markus mentioned the only project downstream from EGit was WindowBuilder so it looks like at least for the EPP packages we should be fine. To be clear on what versions of EGit appeared in which Juno build, it looks like the following (which doesn't match what we thought in the call today): Juno SR0 -> EGit 2.0 Juno SR1 -> EGit 2.1 Juno SR2 RC1: -> EGit 2.1 Juno SR2 RC2: -> EGit 2.1 Juno SR2 RC3: -> EGit 2.2 Juno SR2 RC4: -> EGit 2.3 Matthias please correct if that's wrong. John From: "Konstantin Komissarchik" <[email protected]> To: "'Cross project issues'" <[email protected]>, Date: 02/22/2013 03:26 PM Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay one week, Friday 3/1 Sent by: [email protected] _____ I hate to throw a stick in the spokes, but what happens if another project in the aggregate repository already has a min dependency on EGit 2.2 or even 2.3? - Konstantin From: [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Matthias Sohn Sent: Friday, February 22, 2013 12:15 PM To: Cross project issues Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay one week, Friday 3/1 2013/2/22 David M Williams <[email protected]> After some painful conversation with the Planning Council members, the conclusion was to delay the release 1 week, but not do a full respin, to only revert the EGit contribution. The plan is to redo the common repository and EPP packages, with the EGit contribution reverted to what it was in SR1, which I believe is identical to what it was in RC3. There are a few "technical tricks" I can try to accomplish this, so all other projects do not have to do any re-work ... just wait until Friday 3/1, before making your releases "visible". no, SR2 RC3 contains EGit 2.2.0 [1] which was released in December and SR1 contains EGit 2.1.0 I'd prefer if you could rollback to 2.2.0 but if the planning council decided otherwise be it like that. [1] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?h=Juno _maintenance <https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?h=Jun o_maintenance&id=e5209e06bfbe2284a96b1ce357b9fcd1053072d1> &id=e5209e06bfbe2284a96b1ce357b9fcd1053072d1 -- Matthias_______________________________________________ cross-project-issues-dev mailing list [email protected] <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
