[Starlingx-discuss] [Release] Proposed future release dates

[Jones, Bruce E]

OK, that works too.  LGTM.

Release team, please update the Release Plan and Release sub-team wiki pages.

      brucej

From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com]
Sent: Monday, August 6, 2018 2:15 PM
To: Jones, Bruce E <bruce.e.jones at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: [Release] Proposed future release dates

I propose that we make a exception for the 2018 release as follows:
Release stx.2018.10 code freeze - Sept 26
Release stx.2018.10 - Oct 24

This makes the release available close to the Berlin Summit where it can be announced/socialized (but still we have a 2wk buffer) and gives the team a couple of extra weeks to get into a working model with the proposed sub-project structure and get more bugs and content into the release.

Regards,
Ghada

From: Jones, Bruce E [mailto:bruce.e.jones at intel.com]
Sent: Monday, August 06, 2018 5:03 PM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] [Release] Proposed future release dates

Release team:

At the Ottawa meeting last week, we agreed to change the release cadence from 4/year to 3/year.  Instead of releases in Q1, Q2, Q3, Q4 we'd move to March, July and November.  We also agreed to change the plan from doing two releases in 2018 (August and November) to doing one release in October.

Assuming we continue with our current practice of a code freeze in the 2nd week of the month before the release, and target the release to the 2nd week of the month, we'd end up with the dates below.

Is this OK with everyone?

          brucej


Milestones

Date

Release stx.2018.10 code freeze

Sep 12

Release stx.2018.10

Oct 10

OpenStack Berlin

Nov 7

Release stx.2019.03 code freeze

Feb 13

Release stx.2019.03

Mar 13


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180806/642929ac/attachment.html>