RE: [PEAR-DEV] [RFC2] Handling Backwards Compatibility in PEAR

On 19 Sep 2003 at 23:22, Lukas Smith wrote: > > From: Greg Beaver [mailto:greg@chiaraquartet.net] > > Sent: Friday, September 19, 2003 11:08 PM > [...] > > At this point, package Foo will automatically be considered a > > deprecated package. Foo2 will be intended to eventually replace > > Foo in all installations, and all development of new features on > > Foo will freeze permanently. New development will continue in > > package Foo2. > > > > This solution should only be used if programs that use Foo would > > require a complete rewrite to use Foo2 - if programs that use Foo > > could use Foo version 2.0, then Foo should be released as > > version 2.0, not as a separate package. > > > > In addition, the name of all paths and classes shall change to > > reflect this. > > I don't understand this either. > There is no problem branching off development. I plan to support MDB > 1.x after MDB 2.x has been released. > > I don't see a reason for this regulation. You mean we shouldn't demand that adding new feature to 1.x is frozen? Well, I guess the general intention was that you still bugfix 1.x but if you come up with a 2.x it's not "normal" / likely that you will still spend time adding features to the (old) 1.x - only fixes etc. Stefan