1. Messages
  2. review of DRAFT_Lithium_Release_Plan_ckd

review of DRAFT_Lithium_Release_Plan_ckd

Kent Watsen <kwatsen@...>
 


Overall very good at defining "what", but less so at defining "how".  For instance:

  1. Planning
    • Projects must declare their intent to participate in the Simultaneous Release by M1.
      • How?  Send email to "project-proposals" list with specific Subject line and, in the body of the email, a link to Lithium-compliant release plan?  - in addition to also listing themselves under the "Participating Projects" section on this wiki page?
  2. Leadership & Communication
    • Each project must elect a Project Lead as described in the TSC charter
      • Section 7 of the TSC charter describes voting, but missing from this section is a demonstrable output, such as the project lead's name being added to the projects main page's "Project Facts" boxes, and maybe send an email to a list declaring the choice as well?
  3. Meeting Deadlines
    • If a project cannot make a deadline, the project lead must write a summary of what was missed? why? the course correction that will be taken? and it's impact on other projects?
      • Is this summary to be posted to the Wiki, sent to a list, sent to just dependent projects, or all of the above?
  4. Cross Project Milestone and Release Candidate Reporting
    • It is the responsibility of each projects Simultaneous Release Contact to report both positive and negative statuses
      • How? - by sending email to "release"?  - any specific subject line needed?

Nits:
  1. Introduction
    • OLD: This is a Simultaneous Release Plan for OpenDaylight.
    • NEW: This is a Simultaneous Release Plan for the Lithium release of OpenDaylight.
  2. Leadership & Communication
    • OLD: Each project must elect a Project Lead as described in the TSC charter
    • NEW: Each project must elect a Project Lead as described in the TSC charter, section 7.
  3. Leadership & Communication
    • OLD: The Project Lead will be subscribed to the release mailing list and must respond to requests send to the a timely fashion
    • NEW: The Project Lead will be subscribed to the "release" mailing list and must respond to requests sent to it in a timely fashion
  4. Service Release Participation
    • OLD: All projects participating in the release are also required to participate in the stability releases after the formal release
    • NEW: All projects participating in the release are also required to participate in the stability releases after the formal release (please see  Lithium_Service_Release_Expectations for details)
  5. Meeting Deadlines
    • OLD: If a project cannot make a deadline, the project lead must write a summary of what was missed? why? the course correction that will be taken? and it's impact on other projects?
    • NEW: If a project cannot make a deadline, the project lead must write a summary of what was missed and why, the course correction that will be taken, and it's impact on other projects.
  6. Bugs
    • OLD: Bugs should be filed in Bugzilla
    • NEW: Bugzilla is used to track all bugs in OpenDaylight.   Bugs must be filed for the appropriate project.


Thanks,
Kent
Join {TSC@lists.opendaylight.org to automatically receive all group messages.