Release Engineering Memo [DRAFT]

Release Schedule Template

Milestone 1: Start of the Release (Date: ?)

  • Matz appoints a release manager who will implement the schedule.
  • Matz decides the "must-have" features.
  • Matz approves the target date to release.

between 1 and 2

  • This period focuses on determining feature requests.
    • Some developer meetings should be held to determine requests.

Milestone 2: Feature Request Deadline (Date: about 3 mo. before)

  • All new features must have been accepted.
    • Otherwise, the feature will not be included in the next release.

between 2 and 3

  • This period focuses on implementing the accepted features.
    • It is also good to check bug tickets.

Milestone 3: Feature Implementation Deadline (Date: about 2 mo. before)

  • All features must have been implemented.
    • Otherwise, the feature will not be included in the next release.
  • A preview release is made.
    • Announcements to all developer mailing lists are made.

between 3 and 4

  • This period focuses on fixing bugs.
    • A developer meetings should be held to check all bug tickets.

Milestone 4: Code Freeze (Date: about 1 mo. before)

  • The SVN trunk is copied to branches/
    • All parts in trunk are free to modify.
  • A rc release is made.
    • Announcements to all mailing lists are made.
    • Web site are updated.

between 4 and 5

  • This period focuses on fixing only severe bugs.
    • At least two developers must check a backport patch and agree on it.
    • The (assistant) release managers only commit the branch.

Milestone 5: Final Release (Date: The day)

  • The final release is made.
    • Announcements to all mailing lists are made.
    • Web site are updated.
  • PARTY!!!

References