Re: Protect old branches that are not getting new releases?

2019-04-15 Thread Erick Erickson
Cool, thanks! > On Apr 15, 2019, at 12:12 AM, Adrien Grand wrote: > > This has been implemented: https://issues.apache.org/jira/browse/INFRA-18192. > > On Wed, Apr 10, 2019 at 2:41 PM Gus Heck wrote: >> >> Slightly behind on mails, but I'd like to Echo Erik ... +1 for protection -1 >> for

Re: Protect old branches that are not getting new releases?

2019-04-15 Thread Adrien Grand
This has been implemented: https://issues.apache.org/jira/browse/INFRA-18192. On Wed, Apr 10, 2019 at 2:41 PM Gus Heck wrote: > > Slightly behind on mails, but I'd like to Echo Erik ... +1 for protection -1 > for removal. > > On Fri, Apr 5, 2019 at 11:22 AM Erick Erickson > wrote: >> >>

Re: Protect old branches that are not getting new releases?

2019-04-10 Thread Gus Heck
Slightly behind on mails, but I'd like to Echo Erik ... +1 for protection -1 for removal. On Fri, Apr 5, 2019 at 11:22 AM Erick Erickson wrote: > Protecting those branches would answer the question “If we were to change > the 6.6 branch in order to release a 6.6.7, should I put the changes in

Re: Protect old branches that are not getting new releases?

2019-04-05 Thread Erick Erickson
Protecting those branches would answer the question “If we were to change the 6.6 branch in order to release a 6.6.7, should I put the changes in 6x too” question with “no” ;). Also, if anyone really wanted to re-open 6x they’d have a known state. Well, not 6x since I’m certain some things

Re: Protect old branches that are not getting new releases?

2019-04-05 Thread Adrien Grand
Removing branches proved a bit controversial in the past, see https://markmail.org/message/6ah3m6zd6v3ik3ie for instance. On Fri, Apr 5, 2019 at 3:24 PM Shawn Heisey wrote: > > On 4/5/2019 3:19 AM, Adrien Grand wrote: > > Apparently it is possible to ask INFRA to mark branches as > >

Re: Protect old branches that are not getting new releases?

2019-04-05 Thread Shawn Heisey
On 4/5/2019 3:19 AM, Adrien Grand wrote: Apparently it is possible to ask INFRA to mark branches as protected[1]. Should we do it for branches that are not expecting new releases anymore? I think it would make things less trappy. For instance, backporting to branch_7x is almost for sure a

Re: Protect old branches that are not getting new releases?

2019-04-05 Thread Ishan Chattopadhyaya
+1 On Fri, Apr 5, 2019 at 3:03 PM jim ferenczi wrote: > > +1 > > Le ven. 5 avr. 2019 à 11:20, Adrien Grand a écrit : >> >> Hello, >> >> Apparently it is possible to ask INFRA to mark branches as >> protected[1]. Should we do it for branches that are not expecting new >> releases anymore? I

Re: Protect old branches that are not getting new releases?

2019-04-05 Thread jim ferenczi
+1 Le ven. 5 avr. 2019 à 11:20, Adrien Grand a écrit : > Hello, > > Apparently it is possible to ask INFRA to mark branches as > protected[1]. Should we do it for branches that are not expecting new > releases anymore? I think it would make things less trappy. For > instance, backporting to

Protect old branches that are not getting new releases?

2019-04-05 Thread Adrien Grand
Hello, Apparently it is possible to ask INFRA to mark branches as protected[1]. Should we do it for branches that are not expecting new releases anymore? I think it would make things less trappy. For instance, backporting to branch_7x is almost for sure a mistake since we are not going to release