PATCHES: Countdown for August 26th 2015 - IMPORTANT UPDATE TO PATCH REVIEW PROCESS - PLEASE READ

[James Lowe]

Hello,

***Important do please read***

Google Tracker will be 'read-only' on the 25th August. At the moment,
as I understand it we are still 'transitioning' to a new tracker
system for issues but Rietveld is still working as normal.

This will make keeping track of patches a bit more involved for me to
keep track of current/in progress changes as well as making sure that
I know which patches need (re)testing.

There were some suggestions about sending git formatted patches to
'bug' but as they are all going to probably end up at my feet (so to
speak) I am proposing the following.

After today (August 24th onwards) can we do the following please:


1. For NEW patches (as well as those patches that have had updates,
and so need RETESTING) I'd prefer if they were uploaded to Rietveld as
normal first and then the *URL* to Rietveld issue emailed to me
instead of the git formatted patch. This makes sure that if a patch is
'lost' or 'missed' or 'forgotten' then we still have the Rietveld
issue to fall back on and at the same time we don't clog the dev list
up with patch files of different dates versions.

Put an appropriate string in the subject of the email sent to me like
'PATCH TO TEST' or 'PATCH UPDATED' or something obvious like that and
I'll hopefully do the rest.

Try to use address@hidden email address rather than my gmail account -
I'll monitor both but keeping things in one place is simpler for me.

2. When a patch is tested or re-tested, I'll update the Rietveld issue
with the test results and the patch progress - and I'll update the
Rietveld issue will send the email to the list and the author of the
patch with the test-results.

3. The Patch Countdown email will carry on as normal. With regard to
the 'PATCHES' email; instead of a link to the Google Tracker that
normally get's sent, I'll substitute this with a link to the Rietveld
issue for comments etc.

I'll also keep the same patch-new, patch-review, patch-countdown,
patch-push 'labels' in my test-results as we are all familiar with those.

It will mean that we won't have a 'tracker' to add new issues or for
updates added to existing issues. I'm not sure what the bug squad want
to do with regard to new bugs that need 'tracking', but whatever is
decided on, until we have a working tracker I'd like to make sure that
all patches are fed through me (if that is agreeable) rather than me
have to go and look for them attached to emails or posted on other sites.

If any of your patches are not getting tested or you think are being
missed, just send an email to me rather than complain to the list and
I'll make sure that it is tested/updated etc.

I am not involved with the setting up of the new tracker system so
don't send me questions about that, they can go to the dev-list.


Anyway, here is the current patch countdown list. The next countdown
will be on August 26th.


____________________


PUSH:

Dan Eble: Remove unnecessary min() and max() functions
http://code.google.com/p/lilypond/issues/detail?id=4547

Dan Eble: Don't redefine comparison operators for std::string
http://code.google.com/p/lilypond/issues/detail?id=4546

Dan Eble: Use Grob::programming_error in Semi_tie:: and Tie::less
http://code.google.com/p/lilypond/issues/detail?id=4545

Masamichi Hosada: Fix LilyPond default fonts definition
http://code.google.com/p/lilypond/issues/detail?id=4544

Dan Eble: Add Grob_interface to clean/simplify some things
http://code.google.com/p/lilypond/issues/detail?id=4541

Dan Eble: Rename Grob::pure_height() to pure_y_extent()
http://code.google.com/p/lilypond/issues/detail?id=4540

Heikki: Set the sequence name in MIDI using title information from
\header block
http://code.google.com/p/lilypond/issues/detail?id=4539

____________________


COUNTDOWN:

David Kastrup: Avoid using Offset::arg () gratuitously
http://code.google.com/p/lilypond/issues/detail?id=4551

Dan Eble: Remove dead "!STD_VECTOR" code in flower tests
http://code.google.com/p/lilypond/issues/detail?id=4549

Dan Eble: Eliminate flip(Direction*)
http://code.google.com/p/lilypond/issues/detail?id=4548

Masamichi Hosada: Change the Unicode demonstrations fonts to Libertine
http://code.google.com/p/lilypond/issues/detail?id=952

____________________


REVIEW:

David Kastrup: Small typos in code base
http://code.google.com/p/lilypond/issues/detail?id=4557

David Kastrup: Make Lookup a namespace rather than an empty struct
http://code.google.com/p/lilypond/issues/detail?id=4555

Phil Holmes: Doc: document the extra fields which can be used to
customize the metadata specifically for PDF in \headrer blocks
http://code.google.com/p/lilypond/issues/detail?id=4542

David Kastrup: clusters collapse when applied to repeated chords
http://code.google.com/p/lilypond/issues/detail?id=680

____________________


NEW:

Dan Eble: Group #include directives at top of file
http://code.google.com/p/lilypond/issues/detail?id=4560

Thomas Morley: input/regression/bookparts.ly fails at PDF conversion stage
http://code.google.com/p/lilypond/issues/detail?id=4554

____________________


WAITING:

Urs Liska: Patch: Issue 3916: Add \alternatingTimeSignatures
http://code.google.com/p/lilypond/issues/detail?id=3918

Mike Solomon: Patch: Prevents vertical axis groups with empty skylines
http://code.google.com/p/lilypond/issues/detail?id=3156

Mike Solomon: Patch: Removes the translate_axis call from
axis-group-interface outside-staff positioning.
http://code.google.com/p/lilypond/issues/detail?id=3134

Valentin Villenave: Attach lilypond source in pdf
http://code.google.com/p/lilypond/issues/detail?id=2643

____________________


Thank you,
James