From Fedora Project Wiki
No edit summary |
(Fix info on Spins page) |
||
| Line 31: | Line 31: | ||
** All recurring spins should be in one of the development categories or the upcoming release category. (After a release they should be added back to the spins in development category.) | ** All recurring spins should be in one of the development categories or the upcoming release category. (After a release they should be added back to the spins in development category.) | ||
** Any dropped spin should not be in any development category. It should remain in any appropriate release categories from previous releases. | ** Any dropped spin should not be in any development category. It should remain in any appropriate release categories from previous releases. | ||
** | ** The [[Releases/{{FedoraVersionNumber|next}}/Spins}} | Spins Release page]] for the upcoming release should list exactly the set of spins intended for the next release. Each release this page is copied over from the previous release and recurring spins should have their status set to Pending Spins SIG approval. New spins should be set to Recurring. Dropped Spins should be removed. As spins are approved, their status should be updated. | ||
** The spin pages should reflect the upcoming release. There should be pointers back to versions of the page for all previous releases that included the spin for which the appropriate version can be determined. In practice this will be done going forward, without a lot of effort trying to figure out versions when the spin owner neglected to do this in the far past. | ** The spin pages should reflect the upcoming release. There should be pointers back to versions of the page for all previous releases that included the spin for which the appropriate version can be determined. In practice this will be done going forward, without a lot of effort trying to figure out versions when the spin owner neglected to do this in the far past. | ||
Revision as of 19:32, 10 July 2010
Spins Wrangler (More detailing needed)
Current Spins Wrangler
Overview
The spins wrangler is primarily responsible for escorting spins through the spins processes.
Job duties
- Work with Spins SIG.
- Work with spin owners.
- Work with Release Engineering for alpha, beta and final releases.
- Work with Board for doing spin trademark approvals.
- Review wiki pages (may delegate some work).
- Review spin kickstart files (may delegate some work).
- Regularly attend Spins SIG meetings.
- Read the spins mailing list.
- Make sure current status of spins is accurately reflected in the wiki.
- All spins approved for the next release should be in the next release category.
- All recurring spins should be in one of the development categories or the upcoming release category. (After a release they should be added back to the spins in development category.)
- Any dropped spin should not be in any development category. It should remain in any appropriate release categories from previous releases.
- The [[Releases/41/Spins}} | Spins Release page]] for the upcoming release should list exactly the set of spins intended for the next release. Each release this page is copied over from the previous release and recurring spins should have their status set to Pending Spins SIG approval. New spins should be set to Recurring. Dropped Spins should be removed. As spins are approved, their status should be updated.
- The spin pages should reflect the upcoming release. There should be pointers back to versions of the page for all previous releases that included the spin for which the appropriate version can be determined. In practice this will be done going forward, without a lot of effort trying to figure out versions when the spin owner neglected to do this in the far past.
Schedule
The spins schedule doesn't have tasks specifically tagged for the wrangler, but gives some idea of when things are happening.