Re: Protecting "release--.*" branches

I don't think we need a [DISCUSS] + [VOTE] thread for this subtopic (protecting release branches). This shouldn't be controversial: collaborative branches should be protected. Apache INFRA isn't very fast, so I thought I'd get this going. I think this should make sense regardless of how SIP-12 evo

Re: Protecting "release--.*" branches

Yes sorry I got confused as I had noticed `release--0.31` and assumed SIP-12 said `release--`. I altered the Jira to `release.*` On Sun, Mar 24, 2019 at 11:01 AM David Smith wrote: > Hi John, yes I saw it said "if / is troublesome we suggest using a two > hyphens (--) instead." For personal br

Re: Protecting "release--.*" branches

Hi John, yes I saw it said "if / is troublesome we suggest using a two hyphens (--) instead." For personal branches it makes sense to let users decide how to name their branches, but for "official" and/or protected branches like release, support, hotfix, etc, I think it makes sense to strictly spe

Re: Protecting "release--.*" branches

Hey Dave, The branch naming convention was discussed in SIP-12 . The suggestion was either using '/' or '--' as the delimiter between a prefix and suffix. -John On Sat, Mar 23, 2019 at 9:41 AM David Smith wrote: > I think the discussion