Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGco--Yc5nTW53oGmvrUM6B1hYJicK4XXSpPcUgvDSxJQFCwng@mail.gmail.com>
References: 
 <CAAdrtT1ogRicx47dvJaJ+E_CfakOEMGBZzDqjS2mKJn-CqKJ2Q@mail.gmail.com>
 <CA+faj9xMc6s=eeO1BsG2J-bQq1hy1OPgPgqxPuN9+Eb31S0w5g@mail.gmail.com>
 <94629417818DF4489F3F4B0351579A214DD79D35@SHSMSX101.ccr.corp.intel.com>
 <CAC27z=MNRGDeR60i+Qbx1f2y7KioQ9E4sVHpeuyJGEk6GG3pvg@mail.gmail.com>
 <CAAdrtT1rKHnEno6hhyXhfRQD8dUEA6D6eMfTwaqysnSYiqo+Tw@mail.gmail.com>
 <569636E4.1050705@apache.org>
 <CAKADb_PeuwavZ_PZEPVVYLHzeZ_fnH+aKDMk_sem_ZEZzQ7oAw@mail.gmail.com>
 <3EBEAEBE-E227-4331-93AB-349D9B0A0794@apache.org>
 <8DC2875D-5841-4088-9939-4070158EBA74@apache.org>
 <CAGco--Yc5nTW53oGmvrUM6B1hYJicK4XXSpPcUgvDSxJQFCwng@mail.gmail.com>
From: Maximilian Michels <mxm@apache.org>
Date: Tue, 19 Jan 2016 18:04:42 +0100
Message-ID: 
 <CAGco--bRxEnuW5hoOHW2c8xbqzU7tVHL8waDJG1NynVXFi4SpA@mail.gmail.com>
Subject: Re: [DISCUSS] Git force pushing and deletion of branchs
To: dev@flink.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I've filed an issue at infra to protect the master:
https://issues.apache.org/jira/browse/INFRA-11088

On Fri, Jan 15, 2016 at 3:40 PM, Maximilian Michels <mxm@apache.org> wrote:
> +1 for a protected master.
> +1 for creating release tags under rel/.
>
> On Thu, Jan 14, 2016 at 10:07 AM, Chiwan Park <chiwanpark@apache.org> wro=
te:
>> +1 for protecting all branches including master.
>>
>>> On Jan 14, 2016, at 1:20 AM, Aljoscha Krettek <aljoscha@apache.org> wro=
te:
>>>
>>> +1 on protecting the master
>>>> On 13 Jan 2016, at 14:46, M=C3=A1rton Balassi <balassi.marton@gmail.co=
m> wrote:
>>>>
>>>> +1
>>>>
>>>> On Wed, Jan 13, 2016 at 12:37 PM, Matthias J. Sax <mjsax@apache.org> w=
rote:
>>>>
>>>>> +1
>>>>>
>>>>> On 01/13/2016 11:51 AM, Fabian Hueske wrote:
>>>>>> @Stephan: You mean all tags should be protected, not only those unde=
r
>>>>> rel?
>>>>>>
>>>>>> 2016-01-13 11:43 GMT+01:00 Till Rohrmann <trohrmann@apache.org>:
>>>>>>
>>>>>>> +1 for protecting the master branch.
>>>>>>>
>>>>>>> On Wed, Jan 13, 2016 at 11:42 AM, Li, Chengxiang <
>>>>> chengxiang.li@intel.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 on the original style.
>>>>>>>> Master branch disable force pushing in case of misusing and featur=
e
>>>>>>> branch
>>>>>>>> enable force pushing for flexible developing.
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Gyula F=C3=B3ra [mailto:gyfora@apache.org]
>>>>>>>> Sent: Wednesday, January 13, 2016 6:36 PM
>>>>>>>> To: dev@flink.apache.org
>>>>>>>> Subject: Re: [DISCUSS] Git force pushing and deletion of branchs
>>>>>>>>
>>>>>>>> +1 for protecting the master branch.
>>>>>>>>
>>>>>>>> I also don't see any reason why anyone should force push there
>>>>>>>>
>>>>>>>> Gyula
>>>>>>>>
>>>>>>>> Fabian Hueske <fhueske@gmail.com> ezt =C3=ADrta (id=C5=91pont: 201=
6. jan. 13.,
>>>>>>> Sze,
>>>>>>>> 11:07):
>>>>>>>>
>>>>>>>>> Hi everybody,
>>>>>>>>>
>>>>>>>>> Lately, ASF Infra has changed the write permissions of all Git
>>>>>>>>> repositories twice.
>>>>>>>>>
>>>>>>>>> Originally, it was not possible to force into the master branch.
>>>>>>>>> A few weeks ago, infra disabled also force pushing into other
>>>>> branches.
>>>>>>>>>
>>>>>>>>> Now, this has changed again after the issue was discussed with th=
e ASF
>>>>>>>>> board.
>>>>>>>>> The current situation is the following:
>>>>>>>>> - force pushing is allowed on all branched, including master
>>>>>>>>> - branches and tags can be deleted (not sure if this applies as w=
ell
>>>>>>>>> for the master branch)
>>>>>>>>> - "the 'protected' portions of git to primarily focus on refs/tag=
s/rel
>>>>>>>>> - thus any tags under rel, will have their entire commit history.=
"
>>>>>>>>>
>>>>>>>>> I am not 100% sure which exact parts of the repository are protec=
ted
>>>>>>>>> now as I am not very much into the details of Git.
>>>>>>>>> However, I believe we need to create new tags under rel for our
>>>>>>>>> previous releases to protect them.
>>>>>>>>>
>>>>>>>>> In addition, I would like to propose to ask Infra to add protecti=
on
>>>>>>>>> for the master branch. I can only recall very few situations wher=
e
>>>>>>>>> changes had to be reverted. I am much more in favor of a revertin=
g
>>>>>>>>> commit now and then compared to a branch that can be arbitrarily
>>>>>>> changed.
>>>>>>>>>
>>>>>>>>> What do you think about this?
>>>>>>>>>
>>>>>>>>> Best, Fabian
>>>>>>>>>
>>
>> Regards,
>> Chiwan Park
>>
>>