I will add my opinion as well.... We just added EGit to the JEE epp, and initially had a problem with dialogs on startup that was fixed ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=391377) The fix first appears in 2.2.0
I vote we rollback to 2.2.0 Thanks - Chuck Senior Architect, RAD Java EE Tools, WTP PMC Lead IBM Software Lab - Research Triangle Park, NC From: Matthias Sohn <[email protected]> To: Cross project issues <[email protected]> Date: 02/22/2013 03:15 PM Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay one week, Friday 3/1 Sent by: [email protected] 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&id=e5209e06bfbe2284a96b1ce357b9fcd1053072d1 -- Matthias_______________________________________________ cross-project-issues-dev mailing list [email protected] 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
