Remove Release Edit

This Edit Type deletes a release from the database.

How to do it

• Clicking on the "Delete" link in the sidebar on a release page takes you to a confirmation page where you should enter an Edit Note to justify the removal of the release.

Guidelines

Editing

• Merge duplicate releases:

If two releases have the same track listing and track times, you should do a Merge Releases Edit instead of a RemoveReleaseEdit, following the general rule of Merge Rather Than Delete.

• Cancel accidental edits:

If you entered an Add Release Edit but realize that it was a mistake (perhaps you clicked Submit twice), the quickest fix is to cancel your pending edit (see How To Cancel Edits).

Voting

• Only vote "yes" for RemoveReleaseEdits if they are accompanied by an Edit Note justifying the deletion; otherwise, useful data may be lost.
• If it looks like the release is valid and there are Disc IDs or PUIDs, suggest that the editor should instead Merge Duplicate Releases.
• There are a few exceptions to the general rule that removing releases is rarely correct. One of them (which should be in the Style Guidelines, but probably isn't yet) is for "releases" that have only data tracks. MusicBrainz is a database about Music, and while releases for a Music DVD or a Game Sound Track should be kept, it's OK to remove releases that consist only of Data Tracks (even if they have music files in them).

Notes

This edit is always put to a vote, even if made by an Auto-Editor.

Dependencies

If a release with an open Remove Release Edit is merged into another release, and subsequently the Remove Release Edit passes, the target release of the merge will be removed. This is almost always not the intended result (as both releases are now lost), so avoid competing remove and merge release edits.