Re: PhD release is coming, finish your changes, if you plan any

From: Date: Wed, 27 May 2015 19:28:20 +0000
Subject: Re: PhD release is coming, finish your changes, if you plan any
References: 1 2 3 4  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969385711@lists.php.net to get a copy of this message
On 27 May 2015 at 17:29, Hannes Magnusson <hannes.magnusson@gmail.com> wrote: > On Wed, May 27, 2015 at 9:24 AM, Maciej Sobaczewski <sobak@php.net> wrote: > > Hello Hannes! > > > > W dniu 2015-05-27 o 16:03, Hannes Magnusson pisze: > > > >> On Tue, May 26, 2015 at 11:10 PM, Maciej Sobaczewski <sobak@php.net> > >> wrote: > >> > >>> By the way, I'm wondering if releasing a number of PEAR packages in > 2015 > >>> still makes sense. It requires us to do repetitive work on each release > >>> and > >>> I'm not sure we utilize the benefits (how many people are downloading > >>> individual packages?). However, this should probably be discussed later > >>> and > >>> separately. > >> > >> > >> If you feel its worth it, go for it. > >> > >> -Hannes > >> > > > > What exactly do you mean? Making PhD one, generic PEAR package or > switching > > to composer completely? In second scenario, would a minor version number > > bump be enough? Kalle already suggested it and it seems sensible to me. > > > > I'm not sure what this has to do with versioning. This is just > distribution channels. > Personally, I just tend to use PhD from the Git repo. For those using it via a downloadable package (the doc.php.net PEAR channel at the moment) I don't think switching to Composer (assuming we're not going to be maintaining both distribution channels) will hurt much. It's "composer install" (or some variant thereof) versus "pear install" after all. As someone who has packaged PhD for a (PEAR) release, anything we can do to make our own lives easier would be great: I think Composer would give us that. > > There isn't a huge usegroup for PhD, and the system that use it out > side of php.net haven't upgraded in long long time anyway. > > If you decide on making it a monolithic, or multiple, composer > package(s) I am fine with that. > > I don't remember having installed a standalone app with composer so > unsure how it works, but I trust you know what you are doing so go for > whichever approach you feel is the best :) > > -Hannes >

« previous php.doc (#969385711) next »