Re: next few weeks of development

[Valentin Villenave]

On Wed, Dec 15, 2010 at 6:24 PM, Graham Percival
<address@hidden> wrote:
> You might feel an urge to rush to push stuff onto master right now
> to "get it in before 2.14.0".  Don't.  There will be plenty of
> other releases.  We have way too much new stuff in 2.14.0 as it
> is.  The world will not end if your fantastic fix is "only"
> introduced in 2.14.1.

I get your point, I really do.

However there's a bunch of patches that have been sitting there for a
while: off the top of my head,
http://codereview.appspot.com/74056/
http://codereview.appspot.com/224052/
http://codereview.appspot.com/1659041/
http://codereview.appspot.com/1878048/
http://codereview.appspot.com/1880050/
http://codereview.appspot.com/1914043/
http://codereview.appspot.com/1983047/
http://codereview.appspot.com/2020041/
http://codereview.appspot.com/2145047/ (I feel bad about this one)
http://codereview.appspot.com/2219044/
http://codereview.appspot.com/2220041/ (yes)
http://codereview.appspot.com/2726043/
http://codereview.appspot.com/3334043/

... and that's but what I could come up with with a quick search on
Rietveld. Do we really want to ship a new version without at least
giving these a more proper look?
I for one, couldn't care less whether my vaporware
acciaccatura/NoteNames/HairpinText patches go unmerged for several
stable versions to come. But loosing other people's patches is
definitely something we don't want, even when their authors themselves
seemingly loose interest in getting them merged.

> I'm also invoking my "doc meister" privilege to push doc changes
> without review, so that we can have a quick turnaround between one
> person trying the instructions, me updating the instructions, and
> the next person trying them.  This is not our usual way of
> working, but I think it's worth this special override of our
> normal policy.

Way to go!

Cheers,
Valentin.