Your comments would be very much appreciated.
Current Crappy CVSSyncNeeded Wiki Procedure
===========================================
http://fedoraproject.org/wiki/Extras/CVSSyncNeeded
1. Request new package and branch.
2. Wait until somebody creates empty directories and edits owners.list.
3. Owner checks stuff in and builds.
Using the Wiki for this process has always sucked. We could embed this
process within the Bugzilla review tickets themselves.
Proposal: CVS Admin with Flags
==============================
1) Review is complete, fedora-review+
2) Owner writes in the Bugzilla comment something like:
<Branches> <PackageName> <FedoraAccountName> <BugzillaName>
FC-5 FC-6 foopackage bobjoe bobjoebugzilla@xxxxxxxxx
3) Set fedora-cvs flag to ?
4) CVS Admins get e-mail about fedora-cvs flag. All context of the
review is within the bug itself, so they can easily read all details
about the package and verify approval validity. The Admin then creates
CVS directories and sets owner. Sets fedora-cvs flag to BLANK.
5) Owner checks in and builds.
Benefits
========
- This fedora-cvs flag eliminates the need for CVSSyncNeeded
entirely. An actual work queue with tickets!
- fedora-cvs can be a simple canned query for CVS admins to see.
Awesome possibilities offered via RSS too... =)
- You could also use the fedora-cvs flag with explicit instructions
within any bug to do special requests, like:
"Please remove audacious-itouch. We made some mistake. Blah blah."
Notes
=====
- Unlike other flags, fedora-cvs is only BLANK or ?. fedorabugs members
may request fedora-cvs by setting it to ?. This sends an e-mail to CVS
Admins, signifying that attention is required.
Warren Togami
wtogami@xxxxxxxxxx
--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers
--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
