> was this decision mentioned on this
list ? I wasn't aware of it and
> also can't find
> an announcement in the cross list's
> This means we'll ship EGit 3.1 not with Kepler SR1 but from our own
> updates site
> since 1 month before SR1 already
I'm not sure what to say. Sorry for
not communicating better? Or, I assume Planning Council reps communicate
with the projects they represent? Or, when did you think the deadline was?
Or, should I say, remember we had to
delay Juno SR2 by one week, for the first time ever, due to some last minute
problems due to a project with late feature contributions, no rampdown
plan, no incremental participation in release candidates, etc? That's why
the rule was put in place. It is important we are on time, and it is important
our quality improves each SR; no new problems introduced. That "rule"
is the best concrete thing we could come up with to help ensure that. It
was not a spur of the moment decision, but discussed over several meetings,
with plenty of opportunity for Planning Council reps to solicit feedback
and give advice.
There is no shame at all in releasing
from your own project's repository on your own schedule, if that better
suits your team. Its often a better approach for some.
But, to participate in Simultaneous
Release requires something more ... we have to be well "coordinated"
with each other, to meet the expectations of users and adopters.
So, I have decided ... I will just say,
my personal apologies for not communicating this new rule better,
and in a more timely fashion. I understand how you might have made different
plans if you had known about it earlier. I hope its not too much extra
work for you to adjust your plans, one way or another. Thanks for your
contributions to Eclipse.
Matthias Sohn <matthias.sohn@xxxxxxxxx>
Cross project issues
EGit developer discussion
<egit-dev@xxxxxxxxxxx>, JGit Developers list <jgit-dev@xxxxxxxxxxx>
08/14/2013 02:49 PM
Question on Kepler SR1 release review