Note that we can add this component anytime, but we should probibly wait until pkgdb can manage the modules under it.

Is there a pkgdb2 ticket for handing bugzilla components for the docker image namespace like it does for rpms?

I have now :)

https://fedorahosted.org/pkgdb2/ticket/60

Ok so pkgdb has the code up for review to sync the docker namespace with bugzilla, but the script does not (and I'm not sure it can nor that we want it to) create the product on bugzilla.

So who can add the product to https://bugzilla.redhat.com/enter_bug.cgi?classification=Fedora and what should its name be?

I thought we could via the fedora-admin-xmlrpc account, but it seems I am mistaken. ;(

I've filed an internal ticket asking them to let us do that, or failing that create it for us.

I've copied both of you on it.

The creation of this product is in hand, but for future reference, to create a new Product in bugzilla you need to supply the following, including an initial component (which you change or delete later):

Classification: Fedora

Product:

Description:

Component:

Component Description:

Default Assignee:

Default Description: Default

and (normally) ask for the following additional Group Access Controls:

fedora_contrib: Shown / NA

fedora_contrib_private: Shown / Shown

fedora_pm: editcomponents

redhat: Shown / NA

After it has been created, you can use the fedora-admin-xmlrpc account to edit everything and sync the components.

It is now created.

After you have set up the components, you need to check 'Open for bug entry' on the editproducts page to allow people to open bugs against it.

Many thanks agk!

Nirik, if I understood well, you should be able to turn on filling bugs against that product. Feel free to flip the switch, pkgdb has been updated, so except for testing we're good to go :)

pkgdb has been updated

The components have not yet synced across to bugzilla though.

Replying to [comment:8 agk]:

pkgdb has been updated

The components have not yet synced across to bugzilla though.

That's likely since there are none in pkgdb at this time :)

OK - I've done it another way, enabling the product, but disabling the compulsory component (renamed to 'test') - so as soon as there are components to sync, they'll be usable.

Do you want anything set up for selection in the version field? (or milestones and/or releases)

I think this is all complete aside from versions or milestones... do we know what we want here?

Version should follow Fedora Releases just as RPM content does.

ok. I made rawhide and 25 versions (since I don't think we are doing 24/23).

Let us know if you need anything else on this.