From dev-return-202697-archive-asf-public=cust-asf.ponee.io@tomcat.apache.org Fri Oct 18 14:13:11 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id C22701804BB for ; Fri, 18 Oct 2019 16:13:10 +0200 (CEST) Received: (qmail 45252 invoked by uid 500); 18 Oct 2019 14:13:09 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 45242 invoked by uid 99); 18 Oct 2019 14:13:09 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2019 14:13:09 +0000 Received: from mail-yw1-f54.google.com (mail-yw1-f54.google.com [209.85.161.54]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 44A005A6D for ; Fri, 18 Oct 2019 14:13:09 +0000 (UTC) Received: by mail-yw1-f54.google.com with SMTP id x65so2197650ywf.12 for ; Fri, 18 Oct 2019 07:13:09 -0700 (PDT) X-Gm-Message-State: APjAAAU0EoFW7ocOyxf/KUlU+wYpSrSxQgy8aVRBgZyXN1jV6szX/sgM UuUty/FD7cbiw2fbUtCpLORmYg8eKhaO85up4P4= X-Google-Smtp-Source: APXvYqxQSqZGNxH1GxS/rQ0tqOiIDSb5tP1qAC73xmyl2t1CzVnyaSXUMT/9MG8zXw35HJxCM9dKsDntqx1X859B4gU= X-Received: by 2002:a0d:d606:: with SMTP id y6mr7065655ywd.30.1571407988714; Fri, 18 Oct 2019 07:13:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?R=C3=A9my_Maucherat?= Date: Fri, 18 Oct 2019 16:12:57 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [VOTE] Private branches in the official Tomcat git repository To: Tomcat Developers List Content-Type: multipart/alternative; boundary="000000000000f6f1c905952feeb0" --000000000000f6f1c905952feeb0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Oct 11, 2019 at 4:20 PM R=C3=A9my Maucherat wrote= : > Hi, > > This vote is to regulate the use of branches in the official Tomcat > repository beyond branches that are approved by the community such as 8.5= .x > and 7.0.x. It is possible to do development in private branches directly = in > the official Tomcat repository, as an alternative to using forks and pull > requests. > > Should private branches be allowed in the official Tomcat git repository = ? > [ ] Yes > [ ] No > Here is a recap of the voting. For the binding votes, we have: Yes: michaelo, ebourg, kkolinko No: remm, schultz, rjung, markt Undecided: fschumacher Thanks to the participants, including the ones with non binding votes who were more in favor of branches. So the community is rather split even if the result leans on the negative side, and many liked the idea of feature branches. I think it's not enough to completely forbid branch use beyond the main release branches. Therefore, I propose resolving this as follows: Branches use should follow a non automatic process: - require a significant amount of work with multiple commits ahead to justify their creation =3D always a "feature" branch, with the feature bein= g large enough (which is subjective, use common sense) - get casual community ack before being created (the relevant BZ could get the branch creation request, which should get should get at least one +1 from another committer and of course no vetoes) R=C3=A9my --000000000000f6f1c905952feeb0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Oct 11, 2019 at 4:20 PM R=C3=A9my Maucherat <remm@apache.org> wrote:
Hi,
<= br>
This vote is to regulate the use of branches in the official = Tomcat repository beyond branches that are approved by the community such a= s 8.5.x and 7.0.x. It is possible to do development in private branches dir= ectly in the official Tomcat repository, as an alternative to using forks a= nd pull requests.

Should private branches be allowe= d in the official Tomcat git repository ?
[ ] Yes
[ ] No

Here is a recap of the voting.

For the binding votes, we have:
Yes: michaelo, eb= ourg, kkolinko
No: remm, schultz, rjung, markt
Undecided: fschumacher=

Thank= s to the participants, including the ones with non binding votes who were m= ore in favor of branches.

So t= he community is rather split even if the result leans on the negative side,= and many liked the idea of feature branches. I think it's not enough t= o completely forbid branch use beyond the main release branches.
=
Therefore, I propose resolving this as follows:
Br= anches use should follow a non automatic process:
- require a sig= nificant amount of work with multiple commits ahead to justify their creati= on =3D always a "feature" branch, with the feature being large en= ough (which is subjective, use common sense)
- get casual com= munity ack before being created (the relevant BZ could get the branch creat= ion request, which should get should get at least one +1 from another commi= tter and of course no vetoes)

R=C3=A9my
=
--000000000000f6f1c905952feeb0--