*If* respinning SR2 is in order, is it possible to include m2e 1.3.1 as well (instead of 1.3.0)? This is far less critical than eGit, ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=400520 / http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=95b254ecec2b1cb723a6d2ae4fb7a47a394c2dcb) but it's a very safe change and would spare users the hassle to manually update m2e.
Just saying :-) Fred On Fri, Feb 22, 2013 at 2:31 PM, Oberhuber, Martin < [email protected]> wrote: > +1 for respinning, and declaring Juno SR2 early next week. **** > > ** ** > > Thanks,**** > > Martin**** > > --**** > > *Martin Oberhuber*, SMTS / Product Architect – Development Tools, *Wind > River***** > > direct +43.662.457915.85 fax +43.662.457915.6**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Ian Skerrett > *Sent:* Friday, February 22, 2013 2:19 PM > > *To:* 'Cross project issues' > *Subject:* Re: [cross-project-issues-dev] Reminders for Juno SR2 final > steps**** > > ** ** > > I think we need to look at respinning SR2. For the last 18 months we have > been pushing the entire community towards git, so now introducing a > significant regression into eGit would just be bad news for our users.**** > > ** ** > > ** ** > > ** ** > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Markus Knauer > *Sent:* February-22-13 5:33 AM > *To:* Cross project issues > *Subject:* Re: [cross-project-issues-dev] Reminders for Juno SR2 final > steps**** > > ** ** > > No, I wasn't aware of this bug which is a bit scary, thanks for bringing > it up here on cross-projects. Today I am trying very hard to stay calm, but > it seems that this is not that easy. > > Some of my thoughts... > > - I think it's too late to stop Juno SR2 with this kind of bug. I would > proceed today as planned, everything else seems to involve a very high risk. > - Discuss possible workarounds/solutions for Juno SR2 in parallel... > - If I were a member of the EGit team, I would try to educate my users how > to upgrade to 2.3.1 via wiki, blog posts, newsgroup/forum, mailing list, > other channels... > > Regards, > Markus**** > > On Fri, Feb 22, 2013 at 10:44 AM, Gunnar Wagenknecht < > [email protected]> wrote:**** > > 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 > [email protected] > http://wagenknecht.org/ > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev**** > > > > > -- > > **** > > ### > EclipseSource Group > Telefon: +49 721 664733-0 (GMT +2) > > Telefax: +49 721 66473329 > > http://eclipsesource.com**** > > ** ** > > Innoopract Informationssysteme GmbH > Lammstrasse 21, 76133 Karlsruhe Germany > General Manager: Jochen Krause > Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883**** > > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
