Re: Proposal for Package naming : updating existing non-conform packages

> This would result in a major BC, would it not? Yes it would result in a major BC (different package name + different classname) > Changing any of these would thus result in a major BC, and since Var_Dump is > already at state Stable, you'd have to release a new major > version(PHP_Var_Dump2). Var_Dump is at state 'stable', but it also break the rule about Version Naming (accepted) that - The first release with state "RC" or "stable" must have a version number of "1.0.0". - BC may only be broken in releases ... that have a version number below "1.0.0". So I don't know if it should really be marked at state Stable, or if I'd have to release a new major version in case of BC. > Also, with most rules like this, the older packages NEED NOT conform to it, > if changing it would break BC. Where possible, however, they SHOULD try and > follow these rules. New packages, and additions to existing packages should > ofcourse follow these rules. So I'm going to keep the same name for the package, as it would lead to BC breaks if I renamed it. Regards, --------------------- Frederic Poeydomenge