Re: can I depend on stable PEAR classes to not change?

Culley Harrelson wrote:

On Wed, 25 Aug 2004 08:45:10 +0200, Lukas Smith <lsmith@php.net> wrote:

Maybe here is a relaxing comment: Nobody took anything from you! Its opensource. All past versions are on the server. There is a public CVS server. So there is nothing stopping you from forking the code.

Lukas does this mean I shouldn't trust any of your packages to maintain BC? Your comments make me think that you don't care about your users. That a library is open source does not mean that the maintainers should not feel a sense of obligation to their users. Suggestions like "if you don't like it fork and maintain it yourself" and not practical and a little flippant. Often people are using an open source library because they realize the maintainer is more qualified or has more free time to build and maintain such a library. Giving such people the finger is bad PR for PEAR.

No what I was saying is that we now have regulations and manpower in place to prevent BC breaks. We cannot change the past nor can we gurantee that we dont make mistakes in the future. there may eventually be new major versions which break BC. Usually for some time the old major version will see updates and bug fixes but you do have to accept the fact that deprecated code is likely to see less attention. However nothing is stopping users from asking to be able to takeover the old version. What I am saying is that I want to make it clear that you understand that things have changed for the better in PEAR. However that you will have to expect major version you rely on being deprecated (not removed!). regards, Lukas