Two different release IDs for exactly the same release?

Why do we have two different release IDs for exactly the same release?


The share the same 28 edits, so I assume they are identical?
Why does the “Editing history” for the second release points to the edits for the first release?

How is that possible or useful?

They have most likely been merged.
You never want to delete an id because if someone has tagged thair file using picard and then come back after they have been merged you still want it to work.
In that case it will tell you that the id’s have changed and allow you to save the new correct id back in to the file.

5 Likes

As @dns_server says, those were merged.

https://musicbrainz.org/release/13e88267-0bfc-4622-9f17-789aa26b403a was merged into https://musicbrainz.org/release/8e3658cb-20a6-4522-9f1f-5d0ece3182c1 (I know because it’s where we end up) by yourself, @InvisibleMan78, in Edit #41418793 - Merge releases. :wink:

3 Likes

Thank you @dns_server: That makes sense, indeed!
Thank you @jesus2099: I just want to be sure not to have made a mistake :blush: :innocent:

2 Likes