|Re: [cross-project-issues-dev] Reminders for Juno SR2 final steps|
Greetings,I'm sorry if this has been brought up and discussed elsewhere already. But there is a severe bug in EGit that makes EGit 2.3.0 shipped in Juno SR2 a high risk for users.
See here for details: http://dev.eclipse.org/mhonarc/lists/egit-dev/msg03039.html Am 19.02.2013 18:04, schrieb David M Williams:
This week or next, update your b3aggrcon files with your "final location" so the Juno aggregator could in theory be ran again. We don't plan to, but, you never know. (And, don't forget to update Kepler, if you are using the same input for that.)
Given that there is a severe bug in EGit. Isn't there a chance to update the repo and the packages with EGit 2.3.1?
I understand that it's very late in the game. But the packages will stay there forever on Eclipse.org for download by everbody. Those packages will contain an EGit version that contains a know bug which may delete uncommitted source code in a working copy.
-Gunnar -- Gunnar Wagenknecht gunnar@xxxxxxxxxxxxxxx http://wagenknecht.org/
Back to the top