Re: [PEPr] Comment on RFC::Prefix all packages with P_
| From: | Alexey Borzov | Date: | Thu, 03 Aug 2006 16:31:40 +0000 |
| Subject: | Re: [PEPr] Comment on RFC::Prefix all packages with P_ | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43635@lists.php.net to get a copy of this message | ||
Hi,
Markus Wolff wrote:
Per current guidelines BC breaks are allowed when a package is still in development (below 1.0.0) or when a new major version is started. That hardly qualifies as "let's rewrite everything".Actually, yes. The proposal says: "Changing the class name is considered a BC break. Packages must be updated if a BC break is allowed according to the version naming guidelines [3]." That, together with the headline "Prefix *all* packages..." can very well be interpreted as "yo folks, let's rewrite everything right now".I second Arnaud's opinion - prefix all new packages (+1 for PEAR_ btw.), leave existing packages as they are.With all respect, can you guys actually read the RFC?