[no subject]

It will also mean that problems in the version of
Self_alignment_interface in stable may not be visible in master.

> And a few other issues depend on it, as you can see.
> http://code.google.com/p/lilypond/issues/detail?id=3D3239 (please don't
> look at the tracker description, it's outdated and i cannot change
> it. Look at the Rietveld description
> https://codereview.appspot.com/7768043/ or commit messages).
>
> Note that i don't ask you to review it *now* - i just want to know if
> there is a possibility of getting it reviewed soon.

I don't tell people what they are supposed to review.  If by "review"
you actually mean "committed", then the answer right now is "no".  Not
before 2.18.0 is out, certainly, and preferably not for a while after
that so that the bugs uncovered after 2.18.0 is out have a chance to get
addressed in master in a manner where it is reasonably doable to
cherry-pick them into the stable branch.

> If so, i'd first review it myself, but if it won't get reviewed for
> another 3 months, there'd be no point in me wasting time for working
> on it.

It's pretty safe to say that I would not be happy if it were _committed_
in the next month.  After that, it gets more fuzzy.  With regard to
reviews, the same rules about keeping master as rebaseable as possible
for a while also apply to other contributions, so if you rebase now,
chances are that not much of a further rebase will be needed by the time
including it makes sense.

--=20
David Kastrup