Quoting Pierre-Yves Chibon (2014-09-08 11:55:06)
> On Mon, Sep 08, 2014 at 11:31:58AM +0200, Tomas Tomecek wrote:
> > Quoting Pierre-Yves Chibon (2014-09-05 17:08:39)
> > > 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 and specifies:
> > > - package name
> > > - package summary
> >
> > How about taking this from specfile? (and therefore provide a tool for
> > maintaining specfiles & srpms for reviews)
>
> That would imply parsing the bugzilla ticket to find the spec file and then
> parse it again which itself implies knowing the bugzilla ticket number.
My point was mainly that if you are working on improving the process, there
should be automated as much stuff as possible.
I've read a topic by Mirek Suchy on fedora-devel today about hooking dist-git with
copr and I think that review process could benefit out of it. Roughly, something
like this:
$ fedpkg new-package create-repo
Creating new dist-git repo with sample specfile.
$ ${EDITOR} *.spec
$ fedpkg copr new
Sets owner, project name, arches... and links the repo with copr project
together
$ fedpkg copr build --with-fedora-review
$ fedpkg new-package create-bugzilla
$ fedpkg new-package add-to-pkgdb
This is roughly from top of my head, but I think you'll get my point.
The new-package process would be so much easier (at least to me).
> I think it's just as easy to ask the user to do it.
>
> Note that we have an API endpoint to edit a package's information:
> https://admin.fedoraproject.org/pkgdb/api/#edit_a_package
> and a script to do it in pkgdb2:
> https://git.fedorahosted.org/cgit/pkgdb2.git/tree/utility/update_package_info.py
> (Although we still need to deploy this one in a cron job)
>
> Pierre
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Cheers,
Tomas
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
