Jean-Charles Malahieude <address@hidden> writes:
That's what I feared since the freeze: having to maintain two sets of
translations.
I think that we will likely leave the stable branch behind soon with
regard to documentation maintenance. Our documentation is improving all
the while, and much of it remains applicable to the stable branch. At
the same time, there are several significant changes going forward, and
those will affect a large ratio of documentation, partly
semiautomatically, meaning that cherry-picking changes without extensive
merge conflicts will get harder and harder.
It is important for us to work on documentation designed to match
ongoing work, cater for the future of LilyPond rather than its past. We
don't have two separate teams maintaining stable and unstable branches
(in fact, it is a conflict of interest that I am still responsible for
the stable branch). So I don't really see much of an alternative to
focusing documentation improvements, even where they tend to apply
equally well to past versions, on master. If we have master the best
and most consistent we can make it, this will end up in a stable release
after all. Not 2.16, but 2.18.