Re: Question regarding new package state

luca.mariano@email.it wrote:

Hi all, I'm just rolling the PHP_Fork for uploading into PEAR release system when I got a doubt. What is the correct state & vers. number for a new package? I'm releasing PHP_Fork with state=stable & version=1.0.0 because I not plan any API change (all changes/adjustaments have been made into two years of production use outside of PEAR framework...). Is this correct according to you? Or should I use a devel state for the first release?

Unfortunately the current regulation has been received with some criticism. Then again the "opposition" hasnt formulated a clear alternative either. I have just reopened the discussion on the pear-group ML for this reason. For now simply dont release an RC or stable release as the first release and instead make a release below 1.0.0 with a state that you seem fit (devel, alpha. beta). You can omit the state from the version name if you want. This gives everyone involved to verify that the version in PEAR looks like the one advertised during the proposal phase. But more importantly it gives everyone a chance to see if you configured everything correctly in your package.xml and general file layout etc. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07