#GNOME BUGZILLA HOW TO#
#GNOME BUGZILLA PLUS#
#GNOME BUGZILLA FREE#

Important: Anyone interested in following all bug activity An initial 'general' component has been created.įor any new component QA and default assignee. You (and any other developer of the product) can maintain the product hereĪdjust it to your liking.

Go to the product creation request bug and use the following template to inform the requestor.

Give final instructions in the bug report.

Click Save at the top or bottom of the page.

gnome-panel_developers, and check both checkboxes. Go to the line with the new product name, e.g.

The user page shows the group memberships.

In case developer did not comment in a bug: click Administration->Users, and then fill in the email address (or the first part of it). It will directly take you to the edit user page.

Click on the developers name in the top (header) of the Bugzilla User Info page.

Click on the developers name to go to the Bugzilla User Info page.

In case the product developer commented or filed a bugreport:.

Usually a developer files the product creation request, so check if the creator is one of them.

Find out the login email address of a product developer.

Configure the initial product maintainer.

Set 'Default QA Contact' to the eMail alias created in the step before.

Set 'Default Assignee' to the eMail alias created in the step before.

Set 'Component description' to 'general'.

Users will see this and in a future version users might be able to search for a product using the description. Copying two or three description lines from the product homepage can be a good idea.

Description: Fill in a good description.

Dashes are allowed.Įnsure it has the same name as the tarballs / git repository name Product: fill in the product name in small letters. if a product is a newly created development product, it belongs in Others, not Development! Products not accepted by the release-team must be shown under Other. Click Administration->Products->Add product next to the 'Other' classification.Īdmin, Bindings, Desktop, Development, Platform, and sort of Productivity MUST follow the official GNOME release suites categories. This is the second checkbox, not the first one! In the users screen, give the user access to the ismailinglist group. You will now be able to give the user access to certain groups.

For bugmail: disable bugmail / ensure the checkbox is checked.

GNOME panel maintainer(s))Īs password: run pwgen 20 and copy/paste one of the shown passwords (e.g. As real name: $PRODUCT maintainer(s) (e.g.

Click Administration->Users->Add a new user.Īs login name: $ (e.g.

#GNOME BUGZILLA PLUS#

Having lots of old modules makes daily Bugzilla life more difficult (takes more time to find the right product, more triage time, plus Bugzilla gets slow when it has a lot of products, etc). Having a git module is not enough reason for getting a Bugzilla product, this as products in GNOME Bugzilla will be forever visible. we provide links to GNOME gitĬheck if there is a real need for the productĪ lot of products never get used. GNOME Bugzilla assumes the names are the same.

#GNOME BUGZILLA FREE#

Check the product is Free or Open Source softwareĬheck that the suggested product name matches the git repository name.Check if the product qualifies to be on GNOME Bugzilla.

#GNOME BUGZILLA HOW TO#

Instructions on how to create new Bugzilla products

Gnome bugzilla