Re: Should we dev on master then backport, or the other way?
| From: | Remi Collet | Date: | Fri, 26 Sep 2014 11:42:20 +0000 |
| Subject: | Re: Should we dev on master then backport, or the other way? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-77665@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 26/09/2014 13:29, Florian Margaine a écrit :
> Hi internals,
>
> The question is in the title :-)
>
> As far as I know, most projects follow this convention: develop on
> the master branch, then backport the fixes/features to older
> versions.
>
> I had a discussion with another core dev who told me he did the
> opposite: develop on PHP-5.5, then move the fix/feature up to the
> new branches (first PHP-5.6, then master).
Yes this way.
>
> Is there a convention for php-src? Or is it "whatever the dev
> wants"?
>
See https://wiki.php.net/vcs/gitworkflow
Remi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlQlURwACgkQYUppBSnxahh+aQCffuNOmQJeSSAVjn9lCIx1YMl0
qk0AoOkHVzo7r85HxpxSDn1z98Y4ZVEc
=GRTv
-----END PGP SIGNATURE-----