Re: PEAR_Info...

"Mirco 'meebey' Bauer" <pear-dev@meebey.net> wrote: > this package is great work, but how come that the first official release > in PEAR, the first package you build has package state: stable? > > I dislike ppl saying their first releases they did are stable from the > beginning on... Not everyone releases code they've just started working on. Personally, most of my code is usable the moment it's available because I partake in the little known practice of "testing". :) > also 1.0.1 had already a little bug/mistake in the package and you had > to release a fixed version one day after the original "stable" release, Well, shit happens. > I don't want to blame you or anything, but first releases should be > alpha (if software is completly new) or beta (already testing done...) That imo is up to the developer. One mans alpha is another mans stable. > Stable means that companies will install it on production servers, since > I am Linux-Administrator at work, I really care for state: stable.... Well if you use another persons code, you should be testing it yourself too. :) -- Richard Heyes