Re: OK to release earlier versions first using SourceForge and PEAR

Lukas Smith wrote:

Grant Paton-Simpson wrote:

Hi, Apologies if this is not the right place to send this. I did look but this seemed the best I could find. Is it OK to release earlier versions of classes, e.g. using SourceForge, or one's own website, and then work towards a PEAR release once standards are met? In the earlier cases it would be Open Source but with a voluntary request for donations if people found them useful.

moving this to pear-dev. its Ok my all means. however I would suggest you try to get things into PEAR immediatly. for one it will allow you to use pear cvs earlier. Something that is not required but encouraged. It will also provide you with tons of useful feedback. Also keep in mind that if you are a PEAR newbie you are bound to do things that collide with our CS (coding standards) which might in the end mean BC (backwards compatibility) breaks once you are ready to submit to PEAR.

I would counter Lukas's excellent advice with the suggestion that you work out some of the API issues outside of PEAR, with an ear to the ground (watch how we do things in here). Once the package is ready to consider moving to beta, propose it. This will help to lift up both the quality of the code, and improve the code in PEAR. Code that has to lift itself up by its bootstraps is almost always more interesting and well-written than code that does not - but this depends on the developer as well. Greg