On Tue, May 7, 2013 at 2:56 PM, Bartosz DziewoĆski <matma.rex(a)gmail.com> wrote:
On Tue, 07 May 2013 20:51:07 +0200, Krinkle
<krinklemail(a)gmail.com> wrote:
It is the duty of repository co-owners to make
wise decisions beyond
just code quality. About what changes go in what release (if at all),
whether the introduced features are in the best interest of the users
and that we can maintain them and are willing to support them. And to
be aware of whether a change is breaking or not, and if so if whether
the change should still go in the current release or a the next (e.g.
don't remove/break without deprecation first, if possible).
So in other words, this puts more burden on reviewers, making it harder to
get changes merged, especially for new users?
Because that's what this sounds like. Changes are already rotting in gerrit
for a year (see the recent watchlist thread), and this certainly will not
help.
The current process for release notes is fine; we just need someone to write
a custom merge driver for JGit to avoid the merge conflicts. This is a
technical issue, not a policy one.
As I said many times before, this isn't really necessary since JGit now
supports recursive merges, it's just experimental so I hadn't turned it on.
-Chad