Re: Re: PHP_Beautifier-0.0.6.1 (devel) Released.

From: Date: Fri, 04 Jun 2004 14:33:51 +0000
Subject: Re: Re: PHP_Beautifier-0.0.6.1 (devel) Released.
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-1369@lists.php.net to get a copy of this message
On 4 Jun 2004 at 14:07, Lukas Smith wrote: > David Costa wrote: > > > On Jun 4, 2004, at 2:04 PM, Tobias Schlitt wrote: > > > >> > >> Hi Lukas Smith! You wrote: > >> > >>>>> The new PEAR package PHP_Beautifier-0.0.6.1 (devel) has been > >>>>> released at > >>>>> http://pear.php.net/. > >> > >> > >>>> Uhhh ... are we taking the detail of versions a bit to far maybe? > >>>> 0.0.6.1? > >>>> Well, I was fine with 0.0.6, though I don't know why they didn't > >>>> start > >>>> with > >>>> 0.1.0, but adding another digit is way too much imho. What do you > >>>> think? > >> > >> > >>> yup its not according to the regulations. but i think its enough if we > >>> let him know. > >> > >> > >> Mmmmhhh... Very inconsistent... IMHO we should roll it back and let it be > >> released with the correct version number. That's the only way to make > >> people > >> living that regulation. > > > > > > I agree, this is a candidate for rollback ;) > > well i dont think we should be overly harsh. this package is still > underdevelopment. the developer is new. i think its enough if we inform > the developer. at its current development stage i dont see the issue for > the users as so drastic. however we should make clear that in the future > we will remove releases once we feel that this inconsistency can lead to > issues for users relying on this package. > > we shouldnt use removing releases as a way to beat developers with a > stick. we should only remove releases to prevent issues for pear users. Fully agreed. An additional way I could think of, in cooperation with the maintainer, would be to leave it as is until the next release and remove it afterwards - so once he did the next correct release we could eventually consider removing the current version if he agrees. But since it's not a vital thing that needs removal of the current package maybe it should simply stay as is - it would quite soon be forgotten that there ever was such a release when new versions are out. Stefan

« previous php.pear.qa (#1369) next »