[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Releasing 2.20
Re: Releasing 2.20
Thu, 8 Jun 2017 14:42:49 -0400
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
On 06/07/2017 04:34 PM, David Kastrup wrote:
tomorrow I am leaving for physical therapy.
Hope it goes well David!
So how is it going to end up? Barring objections, I'll probably branch
off a stable release branch early next week. I'll have to see what to
cherry-pick into this branch as fixes proceed, and possibly what to
revert when it is not clear that functionality provided by recent
patches/changes can be considered stable in use and interface.
I don't think that we should need much more than the 3-week maturing
period corresponding to the expected physical therapy duration.
The alternative of releasing 2.18.3 since 2.18.2 does not even compile
using gcc-7 anymore is something I want to avoid.
So I'd rather pitch for a timely release of 2.20. There have been a few
critical bugs flagged, however. I'll take a look at them eventually but
if someone else has a good idea...
Sounds good to me. I have a few things I'd like to get into the stable
release, one way or another, if possible.
- Some CSS edits for the docs that I started but havent
finished/submitted for review yet. I'll try to get that done in the
next few days if I can.
- Might be worth looking again at issue 3884, either to just go with the
initial patch for now, or try for one of the other approaches in that
- This doesn't really matter, but it might be worth renaming the
"staffLineLayoutFunction" context property (which is not really about
staff lines...) to something better, maybe
"pitchToStaffPositionFunction" or pitchToStaffPositionProcedure"? (It
takes a pitch and returns an integer indicating a vertical staff
position. It's used in note-heads-engraver.cc)
Let me know any thoughts on these things,