Re: DB getRow() argument order

Lukas Smith wrote:

Touchy subject. A BC break is a BC break, especially if it doesnt fix a bug this one is quite clear. The thing is just because the recommended way changed a while back doesnt mean that people actually changed their code. Noting this in the changelog is not going to help the people that just want the latest bug fixes and not the latest BC break. Therefore its actually a clear no.

I think it would be really nice to have a package announcement / distribution list, so that if a change like this is going to be made (and it definitely sounds like probably no one is needing the extra param checking logic in getRow()) it could be broadcast to everyone who was registered to receive notices for the package. This could also cover security notices, etc. I use PEAR in production environment for work. I've definitly been burned (i.e. sites break) when upgrades in PEAR do break things -- like latest HTML_TreeMenu no longer working on Safari, all of a sudden. But on the other hand I would be completely fine w/ BC breaking changes as long as I knew about them -- and didn't have to go mucking through the changelog to make sure. I would be one of those people who would definitely register for such announcements for the packages that I use. Also, I think it would be nice if there could be some sort of "what may break!" section of the package.xml that would be manditorily displayed when you upgrade a package using the PEAR installer. Also -- and this is just me being ignorant -- how do you specify the version using the PEAR installer? I have not figured that one out yet... Hans