Re: why is http download alpha?

This is perfectly normal, I wouldn't worry about it - the change from a RC to final stable should have no change other than state and version name (from 1.0RC2 to 1.0, for example) Greg Michael Wallner wrote:

Hi Jeroen Houben, you wrote:

Michael Wallner wrote:

Hi Jeroen Houben, you wrote:

Okay. What changes / additions will it have?

None obvious at this time... :-/ Release 0.2 wasn't even necessary, one could call it a promotion release :-)

Well if there are no API changes planned and not even any additions then it seems to me the code is quite stable. "What's the big deal" you may ask. Well I'm a bit hesitant to use packages marked as BETA let alone Alpha. Alpha means the author can change the API before the package becomes stable which is a good reason to not use the package just yet for any serious project. Looking at http://pear.php.net/manual/en/faq.unstable-code.php I don't think your package is Alpha code. I'd like to see its status changed to at least BETA so people can use it without having to worry about major API changes.

Making a new release just for changing the state seems odd, but I don't know what others think about that... Regards,