Re: (almost-)freezing current master

[David Kastrup]

"address@hidden" <address@hidden> writes:

> Hey all,
>
> To prepare for 2.18, I think we can get it out fastish, but we need to
> more or less freeze current master aside from bug fixes and
> documentation.  I have a lot of stuff on the countdown or on patch
> push that I'm not gonna push for a few months until we get 2.18 out
> (Ferneyhough hairpins, repeat slurs, etc.).
>
> Is everyone comfortable adopting a similar policy?  David has
> suggested 2-months as a possible time frame, which I think is possible
> (there are no egregious, unfixable bugs).  I can hold off this long on
> pushing big patches.  Any longer and it starts to become tedious w/
> rebasing and further work and whatnot, so I am way-for an
> almost-freeze of current master.

Well, if we are all focusing on stuff without major architectural
changes, rebasing should not be a major problem.  A notable exception
are big convert-ly changes: it's usually best to junk every "Run
scripts/auxiliar/update-with-convert-ly.sh" commit when rebasing and
replace it by an actual run.  That can be an actual nuisance.

-- 
David Kastrup