User:CatCat/INSTwave

From MusicBrainz Wiki
< User:CatCat
Revision as of 12:14, 17 January 2022 by CatCat (talk | contribs) (Created page with "instead of vaporwave FISHWAVE! no. Instrument addition stuff! : first the ticket must be selected. usually I square related things of in "mini-version" type ticket, where...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

instead of vaporwave

FISHWAVE! no. Instrument addition stuff!


first the ticket must be selected. usually I square related things of in "mini-version" type ticket, where related tickets are subtickets of that.

  • for new instruments we have new feature/sub-newfeature
  • for tickets that require updating or changing, description or adding aliases we have improvement/sub-newimprovement
  • for actual errors we have bug
  • task is seldom used but occasionally for large unspecific things like "research the difference between these concepts or "translate this wikipage"

when closing the ticket thus is used

  • for fixed finished tickets, just "fixed" and a link to the finished instrument if adding a new one
  • for tickets that are duplicates, just "duplicate" and close them
  • for tickets which are deemed to not be added (usually these are novelties (link to see how to add $ novelties)) just "won't fix"
  • if the ticket does not have enough information and a search on the internet has yielded no usable information, i close it with "incomplete" these can always be reopened if someone has more information and adds it!
  • for situations where something is totally not actionable by me, not an instrument ticket etc, it would be closed as "invalid" (this doesn't happen very often and usually the ticket should be *moved* to the appropriate project)


ticket should have at fixing closing have a link to the instrument and the instrument add should have a link to the associated ticket.