Hej *All*, We from tigermedia support team would kindly ask if it is possible to have the email f...@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=0Bxs12uFOzYYKZE5jSmtxWTBMX0U&export=download] *Glen S. Jensen* *Softwareudvikler* Telefon: +45 96 500 300 | Email: g...@tigermedia.dk Tiger Media A/S | Systemvej 12 | 9200 AAlborg SV <https://maps.google.com/?q=Systemvej+12+%7C+9200+Aalborg+SV&entry=gmail&source=g> | Web: www.tigermedia.dk For supportspørgsmål kontakt os da på supp...@tigermedia.dk eller på tlf. 96 500 300 og din henvendelse vil blive besvaret af første ledige medarbejder. 2018-06-05 12:37 GMT+02:00 Christoph M. Becker <cmbecke...@gmx.de>: > Hi! > > README.RELEASE_PROCESS[1] states in the “Rolling a non stable release > (alpha/beta/RC)” 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 “Forking a new release branch” > 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#L66 > > > [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 > >
