Re: BC solution for Alexey's good point :)

Hi! Lukas Smith wrote:

Clarification: I consider API changes like PHPUnit 0.6 -> PHPUnit 1.0

as

different packages and fully support RFC for these.

Ok so your opposition is actually because of the regulations for what a major release is and not so much about the core of the RFC. As I mentioned before maybe we should therefore separate this regulation from the RFC. Well, after you said this, I understood what my opposition is about, thanks. :]

Yes, what I oppose is lumping together several not-quite-related bits it this RFC and trying to push them in at once on an all-or-nothing basis. I suggest splitting the stuff into several parts and discuss/approve them one-by-one. 1) A guide to version numbering in PEAR. It also should give some hints on what to write in Changelogs and if/when to start an alpha/beta process. Note: it should take into account the current state of affairs both inside PEAR and outside it to minimise confusion! 2) Handling complete API changes. There can also be some sort of document on 3) Creating customized versions of PEAR packages and only then, maybe, if it is *really* needed and is not covered by 1)-3) 4) Handling minor BC breaks.