Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56295
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
MIME-Version: 1.0
Date: Sat, 12 Nov 2011 00:30:00 +0100
Message-ID: <CAH-PCH5j=R2eMex0Z1bwdjy9phi3zcK_A85ck7jgomB_8yQUmg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Cc: David Soria Parra <dsp@php.net>, Philip Olson <philip@php.net>, =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@php.net>, 
	Stanislav Malyshev <stas@php.net>
Content-Type: multipart/alternative; boundary=0016367f94b259697404b17de640
Subject: release-qa.php and README.RELEASE_PROCESS
From: tyra3l@gmail.com (Ferenc Kovacs)

--0016367f94b259697404b17de640
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi.

I mentioned this before, and I remembered yesterday when David updated the
README.RELEASE_PROCESS:
http://svn.php.net/viewvc?view=3Drevision&revision=3D319009 :
Currently bugs.php.net uses the qa.php.net api to decide which PHP branch
are active, so what version should be listed for the bugreports.
As we didn't have any specific api listing the active branches, I guessed
that the active branches will always have an active qa version.
This assumption failed with the release of 5.3.7 when Johannes updated the
next qa version to be 5.3.8, but active =3D> false
http://svn.php.net/viewvc/web/qa/trunk/include/release-qa.php?r1=3D314792&r=
2=3D315141
This made the 5.3 versions disappear from the version list at bugs.php.net:
http://www.mail-archive.com/internals@lists.php.net/msg52793.html
(check the thread or at least my comments)
As I mentioned there, always having an active qa release for the active
branches should fix this issue (there is no need having a release, just
having it active), something like this:
'X.Y.Z' =3D> array(
'active' =3D> true,
'snaps' =3D> array(
'prefix' =3D> 'phpX.Y-latest',
'baseurl' =3D> 'http://snaps.php.net/',
),
),

this seems to be suggested by philip also (I don't know his rationale):
http://svn.php.net/viewvc?view=3Drevision&revision=3D316012

So we can either agree on this (and then I can revert
http://svn.php.net/viewvc/web/php-bugs/trunk/include/php_versions.php?r1=3D=
315166&r2=3D315165&pathrev=3D315166
)
and update the README.RELEASE_PROCESS to reflect this (adding the upcoming
version as active on each stable release and not
adding/removing/inactivating it when we EOLing a branch/major.minor version=
)

I hope this clears up the situation.

ps: having an api for getting the active branches would be still a cleaner,
more straightforward solution.
that would be easy to implement ( returning an array in json from a config
file).

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--0016367f94b259697404b17de640--