Bugfix Releases

After a discussion I've had with someone on the subject of PrefManager, I thought I'd bring it to other developer's attention. >I have to say that I'm seriously considering giving PEAR a miss for >future projects. [...snip...] >I've found serious bugs in most modules excluding DB and PEAR, which >forces me to retain two copies of PEAR - one 'real', the other my >'patched' version. > >This, to mind is just not good practice. And I'd agree with that... I know it's a bit of extra work, but is it possible for more people to backport small bugfixes to the released versions of their packages, and then make a bugfix release. Making a small release (minus the actual coding) takes 5-10 minutes, and upgrading takes even less time, so why aren't people doing it? It's all very well saying "Fixed in CVS" but most people then have to take the CVS version and install it somewhere else, because they don't have write access to the PEAR files. I'm not trying to troll here, just trying to get opinions on release policy. Jon