RE: [PEAR-DEV] [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]

<zitiere wer="Stefan Neufeind"> > Hehe ... sure we ... hmm ... didn't :-)) Well but I think the people > who took place in this discussion could somehow be called current > "core" of the pear-dev-ml, don't you think? Hi Stefan! I disagree with that. There should be no "core" of PEAR. We have the PEAR group as it's official core. That lasts. But I agree that the proposal should be finished. This is OpenSource, so every PEAR attendant has the possibility to read the mailinglist and to give his/her oppinion to an RFC. So, if nobody is quite against a proposal and enought people vote for that, it should become standard. [snip] > maybe someone of the pear-group could raise the > topic again soon in an internal pear group meeting (maybe in IRC or > so). That should IMHO be done. Even though, I do not think that anyone of them is against the solution. > And maybe Greg could also be allowed to participate in that > discussion because he was involved most of us all in working out the > RFC - so that everybody gets his / our explanations right. +1. > And then I hope that when the "taskforce" and the pear-group agree > upon a final "way to go" we're done and can move on to actually do > what we've been talking about :-))) I think this should be handled the normal way: Post a call for votes, count votes after an appropriate time, set standard. ;) 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);');} ?>