tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rémy Maucherat <r...@apache.org>
Subject Re: [tomcat] branch BZ-63905/9.0.x created (now de12b4d)
Date Thu, 07 Nov 2019 22:22:40 GMT
On Thu, Nov 7, 2019 at 11:01 PM Michael Osipov <michaelo@apache.org> wrote:

> Am 2019-11-07 um 22:44 schrieb Rémy Maucherat:
> > On Thu, Nov 7, 2019 at 10:22 PM <michaelo@apache.org> wrote:
> >
> >> This is an automated email from the ASF dual-hosted git repository.
> >>
> >> michaelo pushed a change to branch BZ-63905/9.0.x
> >> in repository https://gitbox.apache.org/repos/asf/tomcat.git.
> >>
> >>
> >>        at de12b4d  BZ 63905: Clean up Tomcat CSS
> >>
> >> This branch includes the following new commits:
> >>
> >>       new de12b4d  BZ 63905: Clean up Tomcat CSS
> >>
> >> The 1 revisions listed above as "new" are entirely new to this
> >> repository and will be described in separate emails.  The revisions
> >> listed as "add" were already present in the repository and have only
> >> been added to this reference.
> >>
> >
> > As has been voted by the community, please refrain from using branches
> for
> > trivial reasons. Thanks.
>
> What is the trivial reason?
>
> Citing yourself:
>
> >
> > 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.
>
> Moreover, no one formally responded to your subsequent proposal.
>

So this means the middle ground solution isn't very interesting to people
in this community, and custom branches are simply not allowed since the
vote was negative.


>
> I don't intend to push n commits to master for unfinished work. I am
> truly convinced that you don't understand the purpose of feature
> branches in a canonical repo. Your Git bits are limited to tomcat.git
> only. Please take a look at other Git repos at ASF, e.g.,
> https://github.com/apache/maven/branches/all.
>
> It should be quite obvious different communities have different processes.

Your commit should be pushed to master, this is how it works in Tomcat
since it is using a simple CTR process. Using a branch means this simple
commit will now generate at least 4 commit emails, plus a useless redundant
discussion about the process. Also, nobody will bother testing until it
gets to master where the CTR rule will still apply even if you used a
branch first.

Rémy

Mime
View raw message