just my 2 cents, but a SR release (bugfix release) that introduces a
known bug that could wipe out all src from the local git repo looks
REALLY bad for Eclipse. The bug itself doesn't look as bad as the
decision to release with it. Perhaps a partial release for packages
that don't ship EGit would be ok, but that seems messy too. If I had
a vote, I'd say "emergency stop" and respin.
In my opinion, "shipping broken but on time" is always more
expensive than "waiting and shipping right", and I don't see any
mitigating factors that might outweigh that cost.
Eric
On 22/02/2013 5:46 AM, Markus Knauer
wrote:
Hi all,
usually releases are quite smooth, but this time it seems to be
different. The issues that have been brought to my attention in
the last 5 hours are very bad news for the Juno SR2 release today:
Bug 400513
- EGit wipes all project source
when staging changes
https://bugs.eclipse.org/bugs/show_bug.cgi?id=400513
Bug 401477
- Cannot find update site for
Juno SR2 bits
https://bugs.eclipse.org/bugs/show_bug.cgi?id=401477
My proposal is to move on with the release today as planned,
but then we need to discuss possible consequences. If you have
any concerns with releasing the packages today, please let me
know very very quickly!
Thanks,
Markus
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
|
