|Re: [cross-project-issues-dev] Announcing a one week slip in the Mars.1 release (from 9/25 to 10/2)|
Surely this is the inevitable consequence of Mars.1 rather than Mars SR1?
SR1 required each component to be a safe upgrade so that exact release timing was irrelevant.
Mars.1 is a new release so users must get to see the co-ordinated new release in one go rather than incrementally. If A.1 pulls in B.1, but C uses B, users of C are in a mess until they get C.1.
On 24/09/2015 05:26, Gunnar Wagenknecht wrote:
Am 23.09.2015 um 23:37 schrieb David M Williams <david_williams@xxxxxxxxxx>: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.
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.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top