> From: Mickael Istria <mistria@xxxxxxxxxx> > To: cross-project-issues-dev@xxxxxxxxxxx, > Date: 09/24/2015 02:10 AM > Subject: Re: [cross-project-issues-dev] Announcing
a one week slip > in the Mars.1 release (from 9/25 to 10/2) > Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx > > On 09/24/2015 07:09 AM, David M Williams wrote: > It's quite important that a "Simultaneous
Release" be simultaneous. > I won't list all those out now, since I suspect obvious to many, > AND, mostly because ... > I'm curious, can you name at least a few ones
if not all?
I'll name only the most important ones. A. There is still a chance we would have to re-spin
AGAIN (small chance, yes, but, you never know). B. In the past, it's caused great user confusion as
well as a lot of bugs being open, which in turn requires some amount of
extra work, when users update some things, and then report "things
don't work" (because they have a "mismatched install") or
questions/bugs from users "I tried to installed such and such, and it says
it needs this and that, but can't find it".
So, seriously, it is important to be "simultaneous",
and from what I've seen, those that don't think so are looking at the world
only from the point of view of their specific project, and not the whole
community of users and adopters -- some of them having installs or use
cases that we would never anticipate.
For those that are not satisfied with the answers
given so far (by me and Max), a more productive conversation would be for
you to ask your questions more concretely. For example, instead of
"why this" or "why not that", it's better to ask something
like "I want to accomplish X, any suggestions on how to do that given
we can not officially release until 10/2?" [For example, I've already
heard about one "everyone is on vacation" case :) -- and, my
friendly answer to that one is "get a backup person!" :) ]
Thanks again to all of you, for your contributions,
attention to quality, and your concern for the users' experience.