Post-Graduation Check List
- The list below summarizes steps a project needs to perform after
-graduation to move out of the Incubator.
-
- PPMC
-refers to the old PPMC for the graduating project,
-
- PMC
-refers to the new PMC under which the graduating project falls (this
-might be the former PPMC for a new TLP), and
-
- Project
-refers to the committers on the graduating project.
-
+
See Gradation Guide.
-
- - Move svn repository from incubator to new location
-
-
- - PMC sends email to infrastructure@ and opens a JIRA issue requesting
-that infrastructure move the svn repository.
-
- - PMC updates the svn-authorization files to provide committers access
-to the newly-named repositories.
-
- - Project verifies all committers have commit access.
-
- - Project removes incubator disclaimer notices.
-
-
-
- - Move web site
-
-
- - PMC emails root@ and opens a JIRA issue requesting UNIX karma for
-committers to access new location on people.apache.org.
-
- - Project verifies all committers know how to and have karma to update
-the new web site.
-
- - Project checks out/deploys the files in the new location.
-
- - PPMC redirects old incubator URL to the new one by editing
-https://svn.apache.org/repos/asf/incubator/public/trunk/site-publish/.htaccess .
-
- - Project verifies the redirect works, then deletes old stuff at
-/www/incubator.apache.org/${PROJECT} .
-
- - PPMC updates http://incubator.apache.org/projects/projectname.html
-with graduation status and link to new website location.
-
-
-
- - Cleanup incubator
-
-
- - PPMC updates http://incubator.apache.org/projects/index.html project
-from "Currently Incubating" to "Successfully Incubated" table.
-
-
-
- - Update JIRA/Bugzilla
-
-
- - PMC emails infrastructure@ requesting that information for the
-project be updated.
-
-
-
- - Move mail lists:
-
-
- - PMC sends email to infrastructure@ and opens a JIRA issue requesting
-that the mailing lists and archives be moved.
-
-
-
- - If the graduating project wants to send out a press release, it must
-be cleared with the PRC.
-
-
- Additional steps for a TLP include:
-
-
- - A new TLP needs board approval. The PPMC creates a proposal including
-a proposed PMC chair and sends that to the board.
-
- - The ASF Chairman sends out an official notice that the board has
-approved a new TLP.
-
- - PMC may then notify infrastructure@ about the new TLP so they can add
-DNS entries (and anything else).
-
- - The mentor or other member updates www.apache.org to add a link to
-the new TLP web site.
-
- - The mentor or other member adds the new PMC to the board reporting
-schedule (update the committee.txt file).
-
- - The new TLP must send monthly board reports for three months after
-approval.
-
-
- Resources include:
-
-