+1 on @tafthorne's suggestion in comment#21 that there be a widget that a maintainer can use to easily swap a private master bug with some chosen public duplicate bug. (Actually, nothing about this widget is specifically about private vs public, but I'll talk about it in those terms here, since this is the current driving use case.)
This widget could be accessible from both the private bug and any public bug marked as a dup of the private bug. Since private->public is a one-to-many relationship here, in the private bug the widget would allow you to select *which* public bug to make be the new master; all current other dups pointing to the private bug could even then be changed to point to the public bug as their new master as well. From the public bug, it could just be a button whose effect is: "Make me the master, thus stealing masterdom from the private bug I'm currently marked as a duplicate of."
+1 on @tafthorne's suggestion in comment#21 that there be a widget that a maintainer can use to easily swap a private master bug with some chosen public duplicate bug. (Actually, nothing about this widget is specifically about private vs public, but I'll talk about it in those terms here, since this is the current driving use case.)
This widget could be accessible from both the private bug and any public bug marked as a dup of the private bug. Since private->public is a one-to-many relationship here, in the private bug the widget would allow you to select *which* public bug to make be the new master; all current other dups pointing to the private bug could even then be changed to point to the public bug as their new master as well. From the public bug, it could just be a button whose effect is: "Make me the master, thus stealing masterdom from the private bug I'm currently marked as a duplicate of."