2.12 out - what now?

[Graham Percival]

There seems to be some confusion about what happens next.  Here's
the plan.

Very short-term (1-2 days):
- John updates webpage to have 2.12 links, news item, etc.
- I send announcement to -user.

Short-term (1 week at most, but start this stuff now as well):
- people commit any "last-minute" stuff to master.  DON'T TOUCH
  STABLE/2.12.
- people DO NOT commit anything which might possibly break stuff,
  including translations.  Sit on those patches for a week.
- At the end of this period, we release 2.12.1 and I send
  announcements elsewhere.

Medium-term (2-4 months, depending on circumstances):
- people commit patches which DO NOT CHANGE THE INPUT SYNTAX (no
  convert-ly rules!) to master.
- people DO NOT COMMIT anything which requires a convert-ly rule.
  Sit on those patches for a month or two.  Stuff them in your own
  private git branch.  Whatever.
- normal doc work occurs, including breaking translations.


After the "medium term", we will have 1-2 months of open season on
patches and input syntax breakage, followed by 1-2 months of
stabilizing and the 2.14 release.  At that time, we will entertain
the notion of "freezing" the code, docs, and whatnot so that
translations and stuff can catch up.  But I said "AT THAT TIME";
so don't argue about that now.

Merry Christmas,
- Graham Percival, new Release Manager for LilyPond