removal of the old PHP-X.Y.Z release branches

9 years ago by Ferenc Kovacs — view source

unread

Hi,

we RMs started using the release branches (PHP-X.Y.Z) a while ago and we
push those so that the we can work together easier when preparing/syncing
the releases.
As those branches are meaningless for the general public I would propose
updating our current release process (
https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS) so that
when we create a new release branch (PHP-X.Y.Z) we also remove the old
release branch (PHP-X.Y.Z-1).
(we could even remove it after tagging the final, but in the past we had a
couple of re-tags, so it is easier to just remove when creating the release
branch for the next version).
I would also propose removing all of the old release branches for now(only
keeping the last one for each minor/major version).

ps: I've also cc-ed the internals@ list so people won't freak out if/when
we remove the old branches en masse.

--
Ferenc Kovács
@Tyr43l - http://tyrael.hu

9 years ago by Julien Pauli — view source

unread

Hi,

we RMs started using the release branches (PHP-X.Y.Z) a while ago and we
push those so that the we can work together easier when preparing/syncing
the releases.
As those branches are meaningless for the general public I would propose
updating our current release process
(https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS) so that
when we create a new release branch (PHP-X.Y.Z) we also remove the old
release branch (PHP-X.Y.Z-1).
(we could even remove it after tagging the final, but in the past we had a
couple of re-tags, so it is easier to just remove when creating the release
branch for the next version).
I would also propose removing all of the old release branches for now(only
keeping the last one for each minor/major version).

ps: I've also cc-ed the internals@ list so people won't freak out if/when we
remove the old branches en masse.

I'm very +1 in cleaning old git references, like RM branches, and not
needed branches like most of "experimental/" , some dating back from

Julien

9 years ago by Anatol Belski — view source

unread

Hi,

-----Original Message-----
From: julienpauli@gmail.com [mailto:julienpauli@gmail.com] On Behalf Of
Julien Pauli
Sent: Thursday, October 8, 2015 5:28 PM
To: Ferenc Kovacs tyra3l@gmail.com
Cc: Stanislav Malyshev stas@php.net; Remi Collet remi@php.net; Kalle
Sommer Nielsen kalle@php.net; Anatoliy Belsky ab@php.net; PHP Internals
internals@lists.php.net
Subject: Re: removal of the old PHP-X.Y.Z release branches

Hi,

we RMs started using the release branches (PHP-X.Y.Z) a while ago and
we push those so that the we can work together easier when
preparing/syncing the releases.
As those branches are meaningless for the general public I would
propose updating our current release process
(https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS)
so
that when we create a new release branch (PHP-X.Y.Z) we also remove
the old release branch (PHP-X.Y.Z-1).
(we could even remove it after tagging the final, but in the past we
had a couple of re-tags, so it is easier to just remove when creating
the release branch for the next version).
I would also propose removing all of the old release branches for
now(only keeping the last one for each minor/major version).

ps: I've also cc-ed the internals@ list so people won't freak out
if/when we remove the old branches en masse.

I'm very +1 in cleaning old git references, like RM branches, and not needed
branches like most of "experimental/" , some dating back from 2000.

Same here with release branches. Once a release is permanently out, it cannot be retagged anyway. If it was bad, the release branch might need to be reused directly. But when branching out the next clean one, the previous release branch loses its usefulness.

Regarding experimental branches - maybe there could be kinda "museum" repository for all that? Even if they wouldn't have any immediate practical usefulness, the thoughts there could be still useful. And, just the history :)

Regards

Anatol

9 years ago by Andrea Faulds — view source

unread

Hey Ferenc,

Ferenc Kovacs wrote:

Hi,

we RMs started using the release branches (PHP-X.Y.Z) a while ago and we
push those so that the we can work together easier when preparing/syncing
the releases.
As those branches are meaningless for the general public I would propose
updating our current release process (
https://github.com/php/php-src/blob/master/README.RELEASE_PROCESS) so that
when we create a new release branch (PHP-X.Y.Z) we also remove the old
release branch (PHP-X.Y.Z-1).

Once a release is made it is tagged, so the branch is then entirely
redundant, right? Or are branches sometimes ahead of the tag?

Assuming the former, then getting rid of the branches once the release
its tagged makes perfect sense to me. Much less needless git clutter.

Thanks.

--
Andrea Faulds
http://ajf.me/

9 years ago by johannes@schlueters.de — view source

unread

Hi,

I would also propose removing all of the old release branches for now(only
keeping the last one for each minor/major version).

what about moving them to a php-src-release.git repo? Keeps the main
repo clean but keeps full history for any archaeological reasons.

johannes

9 years ago by Ferenc Kovacs — view source

unread

On Sat, Oct 10, 2015 at 10:14 PM, Johannes Schlüter johannes@schlueters.de
wrote:

Hi,

I would also propose removing all of the old release branches for
now(only
keeping the last one for each minor/major version).

what about moving them to a php-src-release.git repo? Keeps the main
repo clean but keeps full history for any archaeological reasons.

we have the release tags for that already.
these branches serve no purpose or hold no additional commits after the
release was tagged.

--
Ferenc Kovács
@Tyr43l - http://tyrael.hu