Re: version naming ...

On Tue, 2004-07-13 at 21:22, Ludovico Magnocavallo wrote: > wow, you make me feel almost sorry for having devoted some of time > writing a PEAR library...... not everybody has the time (or the > energy/humour etc.) necessary to keep up with pear-dev. > > But since all our (package authors and maintainers) email addresses are > recorded in the package.xml files, and in countless other places no > doubt, isn't it simple when a new standard gets enforced, to send us an > email asking us to upgrade our packages? > > Or do you prefer the fascist way, ie to delete the package, rendering a > potential disservice to the package's users, and (further) alienating > the authors from the Pear community? > > And if you keep on with this kind of reasoning, and want to delete MY > package (DB_ldap) from PEAR, go ahead who cares, there are tons of > projects/development communities/languages which are more developer > friendly :) > > This said, I have updated my package as soon as I saw a mention of a > "naming convention" for package releases in my inbox (even if I was in a > meeting at the time), so maybe we're not all lost souls..... > > Take care, and maybe relax a bit..... > > Ludo Well thanks for taking ya time and do that so quickly :) But also maybe that's you that have to relax a bit, since deleting the package was only done (or in most cases) to prevent users to install borked things, but it's true that this wasn't the situation this time and shouldn't have been deleted. Guess someone is taking this thing a bit to serious (not you ;)), I agree emailing you would have been enough, maybe there's more behind this then I know, but I doubt this action made PEAR less dev friendly or anything like that, PEAR is just trying to keep it's quality stamp and organization, also this naming stuff wasn't only on pear-dev, but it was also in the news section :) Would be good to read the news section once in a while (do not take this as a order or anything in a bad way :)) Further more no one has anything against your package nor any other package when something like this comes up, nor do are we going to alienate someone from the PEAR community for something like this and rather take steps and try to fix things and do something that fits us all (like now there finally was made better package validation of package.xml when uploading a new release, so something good came out of all of this.) So again thanks for having your great package in PEAR and hope you won't quit developing this package in PEAR just because of this issue ;) And in the future guys, those that have power to delete package, please email the author first before deleting the package if it's such a minor issue that won't affect the user at all (given the author provides a valid/working email.) :D -- Regards Helgi