Not sure how that helps, since you would tag versions anyways using semver, so if there is a master vs next/phpng branch, then they might still result in two tags v1.0 and v2.0 and there is no way to automatically resolve this.
On Thu, Jan 15, 2015 at 3:48 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > Julien Pauli in php.internals (Wed, 14 Jan 2015 18:53:10 +0100): > >This will allow more people to help testing both PHP7 (some people may > need > >some of the top-10 pecl ext to run their apps) and those extensions. > > Some time ago I had a discussion with Mike Wallner and others about a > naming convention for php7/php5.x branches of extensions. It would be > easier to build a lot of extensions for PHP7 if most extension > maintainers used the same names. > > See https://www.mail-archive.com/pecl-dev@lists.php.net/msg02585.html > > Brief summary: > Compiling for php7: use the phpng branch if it exists, otherwise master. > Compiling for php5.x: use the phpog branch if exists, otherwise master. > > Michael used phpng for the php7 branch, but since that discussion I > already see other branch names pop up. I believe a branch 'next' was > introduced in opcache or some extension like that. > > A 'Top 10 Pecl extensions PHP7 compatibility' should at least contain > the name of the PHP7 branch if that is not the master branch. And some > sort of consensus on the names of PHP7 and/or PHP5 branches would be > helpful. > > Jan > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
