Guidelines - 17. Merge Release

17.1.1. The database doesn't currently have a 'Merge Release' function. This functionality may be added at a later date, but in the meantime, please follow the following guidelines if you discover duplicate releases.

17.1.2. For duplicate releases, you should usually put in a 'Remove Release' request for the last submitted version. Make sure to link to the remaining release so users can update their collections. You may also want to check which release has the least number of users with it in their collections or wantlists, and take that into consideration. Please take great care when removing releases, if in doubt about which version to remove, please ask in the Adding & Updating forum.

17.1.3. If the merge is being considered due to bonus items being submitted as separate releases, please first update the main release to represent the whole release, including bonus items. Then put in a remove release request for the bonus item(s). Always make full use of the submission notes / comments on both releases to let everyone know what is happening.