RE: [PEAR-DEV] [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]

Pierre-Alain Joye wrote: > > > > [..] > > > > Don't agree. You seem to always think about dedicated server > > > > environments but what if a hoster has 1000+ users/server > > > and only 40 > > > > rely on package XY which API now has changed. > > > > > > I do not. And I think this hoster should think to install > > > only the core. > > > > Yes you _think_. > > It _should_ be that way - O.K. > > That are a little too much assumptions for my taste. > > The core is what is installed by default with php (sources or binaries). > Actually not exactly the core in the strict sense of the word, but the > plan (still to be discussed) is to do it so in the future majore php > releases. Yes - but that won't clean existing installations. My servers have a lifetime of 3 years before they get exchanged. I won't change the environment before (if there isn't a really good reason). [..] > > > > Just thing about TreeMenu. If the API changes all websites > > > using it to > > > > create the navigation will stop to work. > > > > Now have fun migrating 40 sites at once in one night. > > > > The hoster won't ever be able to migrate to the new version. > > > > > > Explain me what will make you upgrade it suddenly only > > > because a new major version has been released? Did you not > > > see the previous alpha/beta before? > > > > Sorry - maybe I'm wrong but how should I ever migrate to beta if > > it overwrites the stable package? > > It's IMHO exactly the same case as with a stable package. > > Ever heard of development servers and tests suite before switching > things in a production server (or host)? (add smiles) *<8-D OK - let's get back to reality. Where do you think is PHP / PEAR used mostly? The big business, dedicated server, development professional team, project leader, QA team apps or the little - 'I just want to send a mail with attachment', 'I just want to have a tree navigation', 'I just want to use a DB abstraction' apps? And how should there be beta tests on development servers if I am _not_ able to have concurrent versions? Yes - you are right - I'll tell all my hosting clients: 'Hey folks - TreeMenu 3.x is about to be installed because user xy needs it - please adopt your applications and do some beta testing on your development servers!!' 70% of my clients won't even know what I am talking about. And the developer who did the page can't be found anywhere or isn't has left the company. And they won't bill anyone for adopting there homepage if they don't see a benefit. Yes - I don't have userland PEAR and I am not alone with this. So what? Shall I tell them that they should go away or at least not use PHP or PEAR because they aren't professional enough for my servers? That would be a little problem cause they pay my bills... The problem I have with 80% of the programming, os, networking, whatever people is that they don't seem to be able to think in real solutions. They only think how it should be (and really love to point on that whenever possible) and totally ignore the reality: Q: 'Can I restore a deleted file from an ext2 fs?' A: 'Go and restore from your backup tape' Q: 'My database went b0rk because of a power outage - what can I do' A: 'Buy an UPS' This is all mostly the same as in this discussion. You construct a perfect world which doesn't even touch the reality. I still don't know how I could offer my users concurrent versions of a package. I only know that this case never would happen in a perfect world where the 10 employee grocery will buy a devel machine and start unit testing a homepage navigation. regards Daniel Khan