Bug Tracker: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
(list different components (Imported from MoinMoin)) |
Silentbird (talk | contribs) (Edit language and remove part on anonymous reporting (now disabled due to spam)) |
||
| (13 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
<small>[[Development]] > Bug Tracker</small> |
|||
JIRA (https://tickets.metabrainz.org/) is the platform used by the development team and members of the community to track bugs and development progress on the [[MusicBrainz Server]] source code. |
|||
[[MusicBrainz]] uses the [http://www.edgewall.com/trac/ Trac] issue tracker to keep track of bugs and feature requests. |
|||
== Reporting bugs == |
|||
If you find a bug in [[MusicBrainz]], please visit [http://musicbrainz.org/bugs http://musicbrainz.org/bugs]. There you can see if the bug has already been reported, and what progress has been made on fixing it. If your bug hasn't been spotted before, you should probably send an email to musicbrainz-users to discuss it with other users before adding it to the bug tracking system. |
|||
:''Want to report a bug? [https://tickets.metabrainz.org/secure/CreateIssue!default.jspa Report it here!]'' |
|||
To report a bug or unwanted behavior in the server code, [https://tickets.metabrainz.org/secure/Signup!default.jspa create an account] and report it under your name. With an account, you can discuss with other users using comments if more feedback is needed and receive email updates about the bug(s) you've submitted or any other bugs you're interested in keeping tabs on. |
|||
We collect bugs for the following components: <dl><dt>MusicBrainz Server |
|||
<!-- If you do choose to anonymously report a bug, keep in mind that commenting anonymously has been disabled. So in order for you to leave additional information or answer a developers question you will need to either have created an account or manually follow the issue's progress and use the guest account to comment when necessary. The guest account has both username and password set to <code>musicbrainz</code>. |
|||
<dd> |
|||
'''Note''': Some issue may simply be closed if a developer can't get in contact with the reporter (because they submitted anonymously). We ''strongly suggest'' you create an account of your own.--> |
|||
The webserver at [http://musicbrianz.org http://musicbrianz.org]. I believe this refers to the XML webservice, too. |
|||
<dt>Guess Case |
|||
<dd> |
|||
== Workflows == |
|||
The [[Guess Case|GuessCase]] is a sub-component of the webserver and is maintained by [[G0llum]]. |
|||
<dt>MusicBrainz Tagger |
|||
<dd> |
|||
The following are JIRA workflow conventions that the development team uses. |
|||
The old [[MusicBrainz Tagger|MusicBrainzTagger]]. This one is not developed anymore and is superceded by the [[Picard Tagger|PicardTagger]] |
|||
<dt>Picard Tagger |
|||
<dd> |
|||
=== "Decision required" status === |
|||
The [[Picard Tagger|PicardTagger]] is the next generation tagging application and is very actively developed. |
|||
<dt>libmusicbrainz |
|||
<dd> |
|||
The "decision required" status is used when an issue or task requires a decision to be made before developers can move on and start/continue their work. |
|||
The [[MusicBrainz]] [[Client Library|ClientLibrary]]. |
|||
<dt>libtunepimp |
|||
<dd> |
|||
The procedure to follow is: |
|||
the [[MusicBrainz]] tagging application development library. |
|||
# Post a comment that clearly states what needs to be decided. |
|||
<dt>Style Issues |
|||
# Change the status to "decision required" and assign the issue to the person expected to make the decision. |
|||
<dd> |
|||
# When a "decision required" issue is assigned to you, first determine if it's your decision to make. If not, find the right person and re-assign the issue to them. |
|||
# When an issue is your issue to decide and when you've made your decision, note the decision in a comment. |
|||
# Change the status back to open and assign it to the person who should continue to work on the issue (unless in the course of the decision making the task has been passed to someone else). |
|||
== See Also == |
|||
[[Style Issue|StyleIssue]]<code><nowiki></nowiki></code>s are bugs or enhancements to the [[Style Guidelines|StyleGuidelines]] and are maintained by the [[Style Council|StyleCouncil]]. |
|||
* [[How to Report an Issue]] |
|||
<dt>Other |
|||
* [[Development/Git]] |
|||
<dd>Well,anything else... |
|||
</dl> |
|||
| ⚫ | |||
----[[Needs Intertwingling|NeedsIntertwingling]] |
|||
| ⚫ | |||
Revision as of 11:21, 8 January 2019
Development > Bug Tracker
JIRA (https://tickets.metabrainz.org/) is the platform used by the development team and members of the community to track bugs and development progress on the MusicBrainz Server source code.
Reporting bugs
- Want to report a bug? Report it here!
To report a bug or unwanted behavior in the server code, create an account and report it under your name. With an account, you can discuss with other users using comments if more feedback is needed and receive email updates about the bug(s) you've submitted or any other bugs you're interested in keeping tabs on.
Workflows
The following are JIRA workflow conventions that the development team uses.
"Decision required" status
The "decision required" status is used when an issue or task requires a decision to be made before developers can move on and start/continue their work.
The procedure to follow is:
- Post a comment that clearly states what needs to be decided.
- Change the status to "decision required" and assign the issue to the person expected to make the decision.
- When a "decision required" issue is assigned to you, first determine if it's your decision to make. If not, find the right person and re-assign the issue to them.
- When an issue is your issue to decide and when you've made your decision, note the decision in a comment.
- Change the status back to open and assign it to the person who should continue to work on the issue (unless in the course of the decision making the task has been passed to someone else).
