Hi Jonathan, Dropping the bug from this thread since that bug is done and adding the general debian-release list instead. I think that a release team decision is still outstanding. The background is archived at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793316. On Wed, Sep 16, 2015 at 10:09:38PM +0100, Jonathan Wiltshire wrote: > I intend to table some discussion at the next opportunity, probably an IRC > meeting next week, which I hope will begin to get the wheels oiled a little > more. I will see if we cannot put together some thoughts around your > proposals above. I'm sorry I didn't manage to make the previous IRC meeting, but I understand Norvald was there and there was a decision to defer for further consideration. Can I ask that this request (for the release team to make a decision between the choices I outlined[1]) be tabled again at the IRC meeting I understand will be taking place this Wednesday? Please let me know if there's anything I can do to help you make a decision on this. For your convenience, here are those options again: 1) We carry and ship both, which I believe is the preference of the Debian MySQL Maintainers team by default since we do not agree to any other option. We have representatives from both sides who are working together and putting in the work to make this work technically. 2a) We carry both in unstable, but only MySQL in testing. 2b) We carry both in unstable, but only MariaDB in testing. 3a) We drop MariaDB completely, keeping only MySQL in unstable and testing. 3b) We drop MySQL completely, keeping only MariaDB in unstable and testing. The Debian MySQL Maintainers team is prepared to do option 1. But I'd like release team agreement so that we don't have any uncertainty on "which variant should go in the release" or uncertainty around having one of them removed from testing solely on the basis that we are shipping both MySQL and MariaDB. I understand that the security team need to be involved in any decision, so I've Cc'd them also. I feel that this is dragging on excessively now. What can we do to help the release team reach a decision? Thanks, Robie [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793316#57
Attachment:
signature.asc
Description: Digital signature