Am 11.10.19 um 16:43 schrieb Rémy Maucherat: > On Fri, Oct 11, 2019 at 4:30 PM Michael Osipov <micha...@apache.org > <mailto:micha...@apache.org>> wrote: > > Am 2019-10-11 um 16:20 schrieb Rémy Maucherat: > > 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 > > I don't like the term 'private' because everytihing I add to the > canonical repo is intended to merged into upstream sooner or later. > Purely private stuff must be in a fork anyway. > > Please redefine. > > > Well, it's already in the text of the vote ("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"): Private > branches are defined here as any branches whose creation is not > approved and voted on by the community. > > = I feel like creating branch "remm", is it allowed ? > So I say no, because this is the Tomcat repo, not remm's repo, even > though commits could possibly be interesting this is a bit too much.
In that sense, I would say "no", too. There is no need for a private only branch with git. For feature branches - which I understand are out of scope for this - I would be tending towards a "yes". Felix > > Rémy > > > > In that case as depicted by me: > Yes! >
