RE: [PEAR-DEV] [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]
| From: | Tobias Schlitt | Date: | Thu, 25 Sep 2003 14:20:02 +0000 |
| Subject: | RE: [PEAR-DEV] [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft] | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-22005@lists.php.net to get a copy of this message | ||
<zitiere wer="Daniel Khan">
> Fully agree - the whole ruleset is much too complicated to communicate to
> all developers.
What is so complex on it? The package-naming could work mostly transparent
for the developer. If he releases Foo 2.0 the package could automatically be
named Foo_v2. Even the notice about that could appear automatically on the
package website.
The rule about BC breaks only in major versions exists in PEAR for ages and
has only been fully verbalized by Greg.
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);');} ?>