First about Support. We surely will support the customers if they select to run the Drizzle instead of MySQL Server. For us it is same as supporting MySQL Server with custom patches, which we do. In general our Support Policy is very open ended – we would support wide variety of systems, and we’re just being open about our experience with such system and ability to help if need arises.
Will we Recommend Drizzle ? We recommend what makes sense to the customers. If MySQL is not the best choice for the customers we’ll be open about it. Drizzle will need to prove it stable and being better fit for certain group of customers and we will recommend it it in such cases. It is similar to storage engines – will we recommend Falcon or Maria instead of Innodb ? Sure we will, in cases then they will work better. Drizzle is in active development right now and it will take some time before it stabilizes to be ready to be used by wide groups in production.
Will we Contribute to Drizzle ? Our focus with Percona Patchset having MySQL improvements which are ready to be used in production now, which speed things up, improve operations or help analyze performance. We release all out patches as GPL and we would be happy for them to be included in Drizzle or any other MySQL Forks or Patch Sets. Whenever we will have some people actively working on Drizzle remains open question. As customers will be interested in having Drizzle work better on them we surely will do it. We’re also likely to be testing Drizzle to understand sweetspots and problems.