Hi everyone, I wanted to give an update on the original email I sent below. After sending this out, it was decided to make backwards compatibility more of a priority now, and steps are being taken to not force upgrades for any of the releases of Drizzle and libdrizzle.
First, I've added support for the MySQL protocol back into Drizzle and it will start listening on port 3306 along with the Drizzle port. We are going to default back to this port/protocol in libdrizzle sometime soon and this will temporarily be the default protocol for Drizzle. This allows us to keep the Drizzle port free to change and experiment on without interrupting other usage. I'm also going to be keeping API changes in libdrizzle backwards compatible for the time being until the new API is ready, and at that point we'll be bumping the major version of the library. This will require some wrapper and application changes with the new API, but you can continue to use the older versions/API until there is time to port to the new API. -Eric On Wed, Oct 21, 2009 at 02:02:03PM -0700, Eric Day wrote: > Hi everyone! > > I've been focusing on libdrizzle development lately, mainly with new > API, protocol, and keeping in sync with server side changes. Some of > these changes are not going to be backwards compatible, and I don't > think it's worth the effort to support the old deprecated API this > early on. > > When new versions are released, Drizzle will be updated to error > during configure if it depends on the new version. This will be > your cue to either install the latest from lp:libdrizzle or grab the > latest tarball. We are going to try to keep these kinds of upgrades > to a minimum, but I apologize in advance for any inconvenience this > may cause. :) > > I expect at least two or three significant, backwards incompatible > releases in the near future, one for type/command sync with server, > one for the new API, and one for the new protocol. There may be more, > especially with the new protocol work. > > We're also going to start releasing tarballs of libdrizzle on the > same day as Drizzle tarballs (unless nothing has changed), so start > expecting releases more often. > > Thanks! > -Eric _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
