Spins Process

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Timeline)
(Timeline)
Line 40: Line 40:
 
# Bi-weekly reports by Spin Maintainer(s)
 
# Bi-weekly reports by Spin Maintainer(s)
 
# '''Release (GA)'''
 
# '''Release (GA)'''
 +
 +
= Discussion & Proposed Changes =
 +
* https://fedoraproject.org/w/index.php?title=Talk:Spins_Process

Revision as of 20:51, 16 January 2009

Contents

Spins Process

Summary

  1. User submits a spin (kickstart and introduction) to the Spins SIG mailing list at fedora-spins -at- lists.fedoraproject.org, and creates a Spin Page (from the New Spin Page Template).
    • This page is added to category Incomplete_Spins.
    • When the page is ready for review, the page is added to category Spins_Ready_for_Wrangler
  2. Spins Wrangler reviews the Spin Page
    • If accepted, adds it to category Spins_Ready_for_SIG and removes the page from categories Incomplete_Spins and Spins_Ready_for_Wrangler
    • If not accepted, removes the page from category Spins_Ready_for_Wrangler
  3. Spins SIG reviews the Spin
    • If the Spin is accepted by the Spins SIG, the page is added to category Spins_Ready_for_Board
    • If the Spin is not accepted by the Spins SIG, the page is removed from the Spins_Ready_for_SIG category, and goes back to category Incomplete_Spins
  4. The Fedora Project Board decides on Trademark approval (rubber stamp)
    • If the Fedora Project Board approves Trademark usage for the Spin, the Spin Page is added to category Spins_Fedora_X, and removed from category Spins_Ready_for_Board.
  5. Notifications are sent to interested parties (Spins SIG responsibility):
    • The maintainer(s) submitting the Spin
    • Fedora QA
    • Fedora Release Engineering
    • Fedora Infrastructure

Details

Any more details on each stage in the process.

Timeline

  1. Submit spin for review at least 3 weeks before Feature Freeze to allow the Spins Wrangler, Spins SIG and Fedora Project Board to test, review and approve the Spin
  2. Feature Freeze--No more spins accepted for the release
  3. Daily compose tests by Spins SIG, reports go to Spin Maintainer(s)
  4. Bi-weekly reports by Spin Maintainer(s)
  5. Beta Release
  6. Daily compose tests by Spins SIG, reports go to Spin Maintainer(s)
  7. Bi-weekly reports by Spin Maintainer(s)
  8. Preview Release
  9. Release Candidate
  10. Daily compose tests by Spins SIG, reports go to Spin Maintainer(s)
  11. Bi-weekly reports by Spin Maintainer(s)
  12. Release (GA)

Discussion & Proposed Changes