Not the release day email I was expecting to wake up to, but I agree that a
respin seems in order. In this case quality trumps deadlines.
Cheers,
Ian
On 22 Feb 2013 06:19, "Matthias Sohn" wrote:
> 2013/2/22 Gunnar Wagenknecht
>
>> Am 22.02.2013 11:33, schrieb Markus Knauer:
>>
>> - If I were a
2013/2/22 Gunnar Wagenknecht
> Am 22.02.2013 11:33, schrieb Markus Knauer:
>
> - 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...
>>
>
> They are trying really hard. But hones
gt; cross-project-issues-dev-boun...@eclipse.org] *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 ne
...@eclipse.org] 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 t
-issues-dev-boun...@eclipse.org] 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.
This would also help us to properly deal with:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=401477
Cheers
Alexander
Am 22.02.2013 um 11:55 schrieb Gunnar Wagenknecht :
> When it's really too late for SR2, the plan should be made for a SR2a.
--
Dr. Alexander Nyßen
Dipl.-Inform.
Software-Engine
Am 22.02.2013 11:33, schrieb Markus Knauer:
- 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...
They are trying really hard. But honestly, would you download a software
that has a
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
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
2013/2/19 David M Williams
> Don't forget to update "info center docs" if any of you have new docs or
> doc fixes for Juno SR2. You could open a new bug on infrastructure, or
> re-open the one used for original Juno Info Center.
>
I reopened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=379598
t
Now that I've completed my own "final prep", thought I'd remind everyone
else.
There will be no "final confirmation that its ok to release" on Friday.
The general rule is that you should check this cross project list for a
"Wait ... don't release yet" message, but if you do not see one by 9 AM
11 matches
Mail list logo
