Team,

Hopefully you saw my email earlier this week, alerting you to the fact that
the TSC voted to move the date for MS1 out about 1 week to May 2, thereby
enabling project teams to complete their planning for Euphrates at the
plugfest in late April.

I've been updating the Release Milestone Description
<https://wiki.opnfv.org/display/SWREL/Release+Milestone+Description+for+Euphrates>
page to provide more clarity about the requirements for each milestone.
This is based both on an improved understanding of the release process on
my part, as well as some adjustments to the requirements, themselves.
Please take a few moments to review the requirements for MS0 - 4,
especially.

I will continue to work on this as we move forward.  However, for MS1
specifically, I wanted to highlight the requirements, since many of you are
actively working on your release planning.

Requirements for MS1 - release planning

   - Complete a release plan. The format of the release plan is up to the
   PTL and project team.
   - Complete the release plan summary
   
<https://wiki.opnfv.org/display/SWREL/Summary+of+Release+Plans+for+Euphrates>,
   which includes a link to the release plan.
   - Feature projects complete the CI resource requirements
   
<https://wiki.opnfv.org/display/SWREL/Project+CI+Resource+Requirements+for+Euphrates>
    table.

The last bullet is a new requirement for Euphrates.  This requirement is
based on discussions that I've had with the Infra team.  The goal is to
understand the requirements for each participating project, and then to
aggregate those requirements in order to understand the total requirement
for CI resources for the release.

Let me know if you have any questions.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to