Use release disambiguation not release-group disambiguation and more #87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found 2 examples why I would prefer the release disambiguation:
http://musicbrainz.org/release-group/d3f057b4-7e89-3018-9f84-9835ed9b4732
http://musicbrainz.org/release-group/6792b6d1-4e65-3c3c-9d20-d08aa1dcfc60
I did not find an example where the release-group disambiguation would be important (of course, that doesn't prove anything ;))
In release candiate list:
Prefix media with number of media if >1 (e.g. 2xCD, 3xVinyl...) and show MBs disambiguation if set.
Examples:
Candidates:
Candidates: