Yes, I agree there is a large cost with
re-spins and delays. Hence, one of the reasons we are reluctant to do it.
But, given that was the decision, there's several reasons we require participants
to release at the same time. It is not arbitrary nor overly restrictive.
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
We may be talking about different things.
If you have adopters that need to do some final testing, or, do builds
of their own based on your bits, then of course you can tell them were
to find the bits that are anticipated to be released -- I hope you and
others have done that before now! And, they should be told it's tentative
until the formal release. There is always a possibility that by next week
someone will find yet another, much worse bug than what we've seen so far,
and everyone might agree, again, there should be another delay (I think
rare and unlikely, but, not impossible -- especially with our newly relaxed
rules about new projects and new features).
The "visibility" part has
more to do with "users" (not adopters) such as the standard download
pages and p2 repositories should not be "visible" in the normal
ways. Most adopters will know where to find them, on there own!,
but if they don't then the location of the anticipated release bits can
be communicated to them.
Welcome to the business of open source
software development! :)
Cross project issues
09/24/2015 12:26 AM Subject:
Announcing a one week slip in the Mars.1
release (from 9/25 to 10/2) Sent by:
> Am 23.09.2015 um 23:37 schrieb David M Williams <david_williams@xxxxxxxxxx>: > If not obvious, this means all participants in "coordinated release
train" should not make your releases visible on 9/25, but wait until
10/2 10 AM to make them visible, and announce your official releases.
This seem unnecessarily restrictive. I don't bother with the announcement
part. However, I don't recall there is something in the process that requires
project to wait publishing the release bits. Not making them visible could
have a huge effect on a project's adopter community.