On Wed, 2017-05-10 at 21:36 +0200, Michael Osipov wrote: > ...
> > I would still ask for master being mutable (rewritable) or abandon > > the > > concept of a master branch as inapplicable in favor of a release > > branch > > such as 5.0.x. > > One master per major. > > Can you explain why you want master to be rewritable? You will break > all > read-only forks, very annoying for contributors. > > Michael > Different committers have different habits. Some people tend to commit small bits producing a lot of commits and making commit history noisy,difficult to read. This is a ***problem*** for me as a release manager. When I look at the commit history half of it are commits like 'style check fix', 'tab police' and 'javadoc tweak'. I want to be able to rewrite things a little in a time frame of a few days to keep the history sane and manageable. Oleg PS: the problem may go away once everyone gets into a habit of building things in private dev branches and then asking the release manager to merge those dev branches into the release branch. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
