RfC: Gitbox migration; working on branches

[Oleg Kalnichevski <ol...@apache.org>]

Folks

Our repos got migrated to Gitbox. This is great. We can now directly
leverage GitHub pull request and code review functionality among other
things.

There are certain changes, however, we need to adjust to. We can no
longer force push to the master. We can still force push to stable
release branches such as HttpClient 4.5.x, which makes the whole thing
about treating the master differently completely pointless in my
opinion.

Anyway, I would like to propose that the actual development (new
features and bug fixes) be done on a dedicated branch, not directly on
master or stable release branches. This would enable us to review
things before they get merged into the respective release branches.
Pull requests would the preferred way of getting things merged into a
release branch.  

We can decide how pull requests get merged, either by the release
manager or after a certain grace period by the author, or by any other
arrangement we all are comfortable with.

Oleg   






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org