-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rob Wultsch wrote: > On Thu, Apr 30, 2009 at 11:33 AM, Lee Bieber <[email protected]> wrote: >> The Sun Drizzle team got together on Sunday before the MySQL User Conference >> last week and mapped out our next major milestone ("aloha") which is due in >> August. We also spent some time at the beginning of the day defining the Sun >> Drizzle team core values to make sure the Sun Drizzle team is aligned. I >> wanted to share these with you and see if you might have any feedback. These >> may not align directly with your values but we hope these are on target for >> what you might want to see from the Sun team. Please let us know your >> feedback. >> >> Sun Drizzle Team's Project Values >> >> * Have open and well-documented interfaces >> * Have transparent goals and processes, that are communicated publicly >> * Have fun and encourage collaboration >> * Remove barriers to contribution and participation for anyone >> * Enable contributors to build a business around Drizzle >> >> These are documented on the Drizzle wiki at >> http://drizzle.org/wiki/Sun_Drizzle_Team_Values >> >> For the upcoming aloha release in August we are still focusing on building a >> solid platform and architecture so most of the blueprints that are targeted >> for aloha fall into those areas. The list for aloha can be found at >> https://launchpad.net/drizzle/+milestone/aloha. We are still filling in some >> of the details but look for continued improvements in plugins, protocol, >> replication, benchmark automation framework and general code clean up. Would >> love to hear your feedback in case we are missing anything from your >> perspective. >> >> Thanks, Lee >> > > " Remove Virtual Column (vcol) code " > > Any particular reason?
The original author was not willing to maintain the code, and it had inherent problems and would not pass some of the tests in the test suite. Additionally, the code was not particularly modular. I think a module which implemented virtual columns would be a much better solution, since if a module developer ceased to maintain the module, the kernel would no be affected. > Also, will the drizzle replication system try to appear to appear to > be similar in form to the current mysql system? Cause that would be > awesome for adoption. The SQL API (i.e. how you start/stop/manage slaves and such) will likely be very similar (or easier even). Internally, the Drizzle replication schema is entirely different, though... More on replication stuff will be coming out in a few weeks... :) Cheers! Jay > -- > Rob Wultsch > [email protected] > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn6gQEACgkQ2upbWsB4UtFX7QCfanpY5RItB2mENvE5StyKalLW hekAnA5o3Q42MC5IbHVW4vQvMbX9wekG =ZvV7 -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
