On 26/06/2022 01:04, David Kastrup wrote:
Colin Campbell <c...@shaw.ca> writes:
From the shores of Jarvis Lake in the foothills of the Rockies, here
is the current countdown list.
The next countdown will start on June 27th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1374 configure.ac: Fix test ... == ... bashism - David Kastrup
https://gitlab.com/lilypond/lilypond/-/merge_requests/1374
Ok, what did I do wrong here to have this still on the list? This was
pushed 4 weeks ago.
It seems to me that the entire list is from weeks ago. I ran
countdown.py locally
and it gave this:
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
No patches in Push at this time.
Countdown:
!1432 changes.tely: Remove redundant entry - Werner Lemberg
https://gitlab.com/lilypond/lilypond/-/merge_requests/1432
!1431 Color support for color-blind people - Werner Lemberg
https://gitlab.com/lilypond/lilypond/-/merge_requests/1431
Review:
!1427 Consolidate version processing in Python scripts - Jean Abou Samra
https://gitlab.com/lilypond/lilypond/-/merge_requests/1427
New:
!1426 Info: build: resolve build issues concerning compiled bytecode -
John Wheeler
https://gitlab.com/lilypond/lilypond/-/merge_requests/1426
Waiting:
!1434 Drop support for GCC < 5 - Dan Eble
https://gitlab.com/lilypond/lilypond/-/merge_requests/1434
!913 release: binaries with cairo - Han-Wen Nienhuys
https://gitlab.com/lilypond/lilypond/-/merge_requests/913
(Note that the patches in Push don't appear as they have already
been pushed.)
Colin, my guess is that you accidentally reused a draft from your
other camping trip around the time of
https://lists.gnu.org/archive/html/lilypond-devel/2022-05/msg00132.html
Best,
Jean
