Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102163
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain tigermedia.dk designates 74.125.82.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <e2831e81-4829-b1ba-51eb-87de47793432@gmx.de>
References: <e2831e81-4829-b1ba-51eb-87de47793432@gmx.de>
Date: Tue, 5 Jun 2018 12:49:04 +0200
Message-ID: <CAEch_uhWKwKXxjNtMnzVA+D1Or0XBbUc=ehv=i-c_sUn6jiq=Q@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000008aaff8056de2cc4f"
Subject: Re: [PHP-DEV] README.RELEASE_PROCESS: misleading branching info?
From: gsj@tigermedia.dk ("Glen S. Jensen")

--0000000000008aaff8056de2cc4f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hej *All*,

 We from tigermedia support team would kindly ask if it is possible to have
the email fb@tigermedia.dk removed from the PHP internals list as the mail
is no longer in use. And every mail is fowarded to our support. We have
tried to remove it from the list our selves, but we don't have the required
credentials to login to the associated account :)

We apologize in advance to all the list members that are not related to
this issue. We didn't know how else to proceed :(


Med venlig hilsen / Kind regards
[image: uc?id=3D0Bxs12uFOzYYKZE5jSmtxWTBMX0U&export=3Ddownload]

*Glen S. Jensen*
*Softwareudvikler*

Telefon: +45 96 500 300 | Email: gsj@tigermedia.dk

Tiger Media A/S | Systemvej 12 | 9200 AAlborg SV
<https://maps.google.com/?q=3DSystemvej+12+%7C+9200+Aalborg+SV&entry=3Dgmai=
l&source=3Dg>
|
Web: www.tigermedia.dk

For supportsp=C3=B8rgsm=C3=A5l kontakt os da p=C3=A5 support@tigermedia.dk =
eller p=C3=A5 tlf.
96 500 300
og din henvendelse vil blive besvaret af f=C3=B8rste ledige medarbejder.


2018-06-05 12:37 GMT+02:00 Christoph M. Becker <cmbecker69@gmx.de>:

> Hi!
>
> README.RELEASE_PROCESS[1] states in the =E2=80=9CRolling a non stable rel=
ease
> (alpha/beta/RC)=E2=80=9D section[2]:
>
> | 4. Checkout the release branch for this release (e.g., PHP-5.4.2) from
> | the main branch.
>
> However, it seems that the PHP-x.y.z release branch is usually only cut
> shortly before GA[3].  Furthermore, the =E2=80=9CForking a new release br=
anch=E2=80=9D
> section states that the PHP-x.y branch is supposed to be cut shortly
> before the first beta release[4].
>
> So what is the proper procedure here?
>
> [1] <https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS>
> [2] <https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS#L6=
6
> >
> [3] <http://news.php.net/php.internals/101084>
> [4]
> <https://github.com/php/php-src/blob/master/README.
> RELEASE_PROCESS#L338-L341>
>
> --
> Christoph M. Becker
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000008aaff8056de2cc4f--