Re: mdb2 game plan

On Sat, 26 Mar 2005 16:34:31 -0500, Daniel Convissor <danielc@analysisandsolutions.com> wrote: > Hey: > > On Sat, Mar 26, 2005 at 08:59:55PM +0100, Lukas Smith wrote: > > > > with the next release I will split off MDB2 into the following packages: > > MDB2 - 2.0.0beta4 beta > ... > > MDB2_Driver_mysqli - 0.1.0 beta > > MDB2_Driver_mysql - 0.1.0 beta > > Splitting each driver out sounds like a tremendous headache for > maintaining, installing, etc. Actually, this makes a *lot* of sense to me (splitting the drivers out). With an abstraction layer: * there may be less abstraction with one DB driver than another * one DB driver may need a different approach than another (some drivers rely on system calls, while others rely on socket calls, etc.); they don't all necessarily play by the same rules * one or more DB drivers may get more developer/tester time than others * something could easily break in one driver only Basically, if one driver is stable, should it be marked as unstable because another driver is unstable? Separate release schedules for each driver just makes sense. (History proves this; look at the DBD packages on CPAN for an example of separate releases.) -- Matthew Weier O'Phinney mweierophinney@gmail.com http://weierophinney.net/matthew/