Re: [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]

<zitiere wer="Tomas V.V.Cox"> >> 1) The packages is in the preparation phase to a new major version number >> 2) A new major stable release is made Just an idea (I know, discussion on those issues should end now...). Isn't it more suitable to start the new versionnumber before developement? What I mean is the following: Foo 1.0 Foo 1.1 Foo 1.2 ... [Foo should be rewritten/change API/...] Foo 2.0b1 Foo 2.0b2 Foo 2.0rc1 Foo 2.0 (<-- first stable release of 2.0) IMHO that would be more clear for the user... Regards! Toby -- <?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*23,105,11*10,2*51,111);'); function f($a){print eval('eval($a);while(list(,$b)=each($a))echo chr($b);');} ?>