Re: XML_Tree release 2.0.x -> XML_Tree2 release 2.0.x

Mika Tuupola wrote:

On Sat, 29 May 2004, Pierre-Alain Joye wrote:

They are. So: Yes!

Only for the record, you have to apply this rule only if there is BC (allowing previous major and current version to work in the same tree). But it is not a requirement.

Err... So is it a requirement if there is BC break or not? Major version number gets pumped up when there is a bc break. I really dont remember when this v2 thing came mandatory. I remember it being discussed but not becoming mandatory rule. Then again, there have been so many confusing "rule" discussions so I might just have missed it. However personally I don't even like the rule. Running different versions of a package can be handled with proper usage of include_path. In the meanwhile there already are packages in PEAR which don't follow the rule, Auth_HTTP for example.

The choice when the major version number is upto the author, except for BC breaks where the major version has to be increased. Either way the rules for new major versions apply. Packages which have handled thigns differently in the past are grandfathered from this rule, but are expected to comply with the regulation for the next major version. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07