Re: XML_Tree

Helgi Þormar wrote:

On Fri, 2005-04-22 at 15:41 +0200, Willo van der Merwe wrote:

Could we release XML_Tree? It's been in RC2 for almost a year now.

Nope we can't v2 breaks BC and we are kind stuck in a loop in regards what to do. Many users are using v2 even tho it's beta and we can't move it to XML_Tree2 since then it would break to much for existing users when they upgrade ... Well anyway it has been discussed what to do and no solution was found, so it has to stay like this until we know what to do. Any QA/Developer knows what to do ?! Speak up then, I ran few ideas with Davey the other day and he came up with few but the conclusion was that none of them would at least give half of XML_Tree users a hard time when upgrading :/ Well helgi, I guess that you're in the same situation as i was with Crypt_RC4. After a small discussion with Arnaud and Matthew we decided to split up the version. Within a few weeks Matthew will create a new packahe called crypt_rc4v2, i guess that what's has to happen woith xml_tree too.

On the other hand, the pear installer (or upgrader if you like) can work in two ways. First, a administrator tells pear exactly what package(s) to update. The other way is what i call the 'windowsupdate' way. the pear installer get the current list with packages from the server and update all packages which have a newer version. Developers/companies/administrators who are using the first way, will (hopefully) always test a newer version of a software package to find any potential problems. They will notice the BC break and NOT update to the new (v2) version. I know companies that have put the pear upgradeall in the crontab, so they can say, we're always running the lastest version. Most of the time these are also know as hosting partners. And that brings us to the core of the problem. There are a lot of developers can cannot force an ISP or hosting provider to run a specific version of a software package. So the only 'safe' solution to the problems is to create a new package.. I know, as a developer i really dislike this way of development. Except for the packages that come with PHP, i haven't installed any other packages globally on my machine. For each website i simply create a directory 'pear' and put all the pear packages that I need for that website in there. This all under the motto 'if it ain't broken, don't fix it'.. ;-) Regards, Dave Mertens