|Re: [cross-project-issues-dev] Reminders for Juno SR2 final steps|
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.
2013/2/22 Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>Am 22.02.2013 11:33, schrieb Markus Knauer:They are trying really hard. But honestly, would you download a software that has a disclaimer next to the download link which says "hey, this is broken; you need to update afterwards"? IMHO, in the current state of SR2, such a disclaimer has to be put somewhere on the download page.
- 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...
When it's really too late for SR2, the plan should be made for a SR2a.+1what's the authority which can decide this ? Let me know when a decision is made,I'll standby to update our contribution for Juno SR2 or SR2a to EGit 2.3.1.--Matthias
cross-project-issues-dev mailing list
Back to the top