New package, new branch, new workflow?
By Pierre-Yves on Wednesday, July 23 2014, 09:28 - Général - Permalink
If you are a Fedora packager, you are probably aware of the new pkgdb.
One question which has been raised by this new version is: should we change the process to request new branches or integrate new packages in the distribution.
The discussion has occurred on the rel-eng mailing list but I'm gonna try to summarize here what the process is today and what it might become in the coming weeks.
Current new-package procedure:
- packager opens a review-request on bugzilla
- reviewer sets the fedora-review flag to ?
- reviewer does the review
- reviewer sets the fedora-review flag to +
- packager creates the scm-request and set fedora-cvs flag to ?
- cvsadmin checks the review (check reviewer is a packager)
- cvsadmin processes the scm-request (create git repo, create package in pkgdb)
- cvsadmin sets fedora-cvs flag to +
New procedure
- packager opens a review-request on bugzilla
- reviewer sets the fedora-review flag to ?
- reviewer does the review
- reviewer sets the fedora-review flag to +
- packager goes to pkgdb2 to request new package (specifying: package name, package summary, package branches, bugzilla ticket)
- requests added to the scm admin queue
- cvsadmin checks the review (check reviewer is a packager¹)
- cvsadmin approves the creation of the package in pkgdb
- package creation is broadcasted on fedmsg
- fedora-cvs flag set to + on bugzilla
- git adjusted automatically
Keeping the fedora-cvs flag in bugzilla allows to perform a regular (daily?) check that there are no fedora-review flag set as + that have been approved in pkgdb and whose fedmsg message hasn't been processed.
Looking at the number, it looks like there are more steps on the new procedure but eventually, most of them can be automated.
New branch process
For new branches, the process would be very similar:
- packager goes to pkgdb2 to request new branch
- requests added to the scm admin queue
- cvsadmin checks the request (requester is a packager...)
- cvsadmin approves the creation of the branch in pkgdb
- branch creation is broadcasted on fedmsg
- git adjusted automatically
Comments
Overall it looks like the new procedure actually saves the manual step of cvsadmin setting fedora-cvs+. The other "added" steps don't look like manual steps, as you pointed out. And new branches look pretty easy too.