Re: Milestones
Am Sonntag, den 11.10.2020, 12:12 -0400 schrieb Dan Eble: > On Oct 11, 2020, at 10:33, Jonas Hahnfeld wrote: > > 2.21.7 has already been built and tagged (see git), the commits will > > I need a little more help than "see git". I was referring to the new tag in the repository, which gives a pretty noticeable line on git fetch / pull (in my opinion): * [new tag] release/2.21.7-1 -> release/2.21.7-1 > I can see, after the fact, a merge from release/unstable into master that > updated the version. I guess I need to check the release/unstable branch > before I merge an MR with new regression tests to master. Is that right? Yes, or in this case the MR to merge release/unstable was already posted (but not merged yet). Jonas signature.asc Description: This is a digitally signed message part
Re: Milestones
On Oct 11, 2020, at 10:33, Jonas Hahnfeld wrote: > > 2.21.7 has already been built and tagged (see git), the commits will I need a little more help than "see git". I can see, after the fact, a merge from release/unstable into master that updated the version. I guess I need to check the release/unstable branch before I merge an MR with new regression tests to master. Is that right? — Dan
Re: Milestones
Am Sonntag, den 11.10.2020, 10:19 -0400 schrieb Dan Eble: > I do not understand which version/milestone to use when I add regression > tests and close a merge request or issue. > > To pick a specific example, > https://gitlab.com/lilypond/lilypond/-/merge_requests/445 > > The MR added regression tests with \version "2.21.7". The VERSION file says > this: > > MAJOR_VERSION=2 > MINOR_VERSION=21 > PATCH_LEVEL=7 > MY_PATCH_LEVEL= > VERSION_STABLE=2.20.0 > VERSION_DEVEL=2.21.6 > > But the milestone for the MR now set to 2.21.8. The milestones track which version fixed / will fix the issue, they're an exact replacement for the old Fixed_x.y.z labels on SourceForge. As 2.21.7 has already been built and tagged (see git), the commits will appear in the next version. (I hope that'll be 2.21.80 or the like, but I needed something right now so I went with what VERSION will say.) Jonas signature.asc Description: This is a digitally signed message part
Milestones
I do not understand which version/milestone to use when I add regression tests and close a merge request or issue. To pick a specific example, https://gitlab.com/lilypond/lilypond/-/merge_requests/445 The MR added regression tests with \version "2.21.7". The VERSION file says this: MAJOR_VERSION=2 MINOR_VERSION=21 PATCH_LEVEL=7 MY_PATCH_LEVEL= VERSION_STABLE=2.20.0 VERSION_DEVEL=2.21.6 But the milestone for the MR now set to 2.21.8. — Dan
PATCHES - Countdown for October 11th
Hello, Here is the current patch countdown list. The next countdown will be on October 13th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !445 midi2ly.py: handle a piece without notes - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/445 !444 Fix -d clip-systems in SVG backend - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/444 !443 Annotate ly_wrong_smob_arg with [[noreturn]] - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/443 !442 lilymidi.py: fix key signature conversion - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/442 !441 RepeatTie and LaissezVibrerTie have tie-interface - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/441 !440 Clarify documentation of \with-outline vs. \with-dimensions[-from] - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/440 !439 Tweak piece of advice for finding failed files in make test - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/439 !437 Restore things missing from MusicXML regtests - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/437 !436 Ottava markups: Do not emit unneccessary warning - Michael Käppler https://gitlab.com/lilypond/lilypond/-/merge_requests/436 !435 Text replacements are not recursive (fixes #6050) - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/435 Countdown: !450 Regression test for clash between opposite stems from different staves - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/450 Review: !418 CG: Revise Git documentation - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/418 New: No patches in New at this time. Waiting: !449 Stepmake / po-targets: Clean up - Michael Käppler https://gitlab.com/lilypond/lilypond/-/merge_requests/449 !447 RFC: Rethink horizontal alignment of mid-staff bar numbers - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/447 !438 Revise handling of "no music in score" scenarios - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/438 !344 doc: fully qualify doc includes. - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/344 !204 Move parallel processing to lilypond-book - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/204 *** Regards, James