Here is the current countdown report.
The next countdown will begin on February 15th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1838 NR: Link 'Clef styles' appendix to 'Clef' section - Werner Lemberg
h
On Mon, Feb 13, 2023 at 11:53 AM Jean Abou Samra wrote:
>
> Le lundi 13 février 2023 à 11:07 +0100, Han-Wen Nienhuys a écrit :
>
> Hi there,
>
> Every year, we go over the source code to update the copyright years
> that are found in the source headers. I propose to stop this.
>
> We started doing
On Mon, 2023-02-13 at 13:36 +0100, Janneke Nieuwenhuizen wrote:
> Han-Wen Nienhuys writes:
>
> Hey,
>
> > Every year, we go over the source code to update the copyright years
> > that are found in the source headers. I propose to stop this.
>
> +1
>
> > Also note that many other projects (eg. g
Hi Werner.
> Hello Jose,
>
>
> below is something for GNU LilyPond.
I just updated the ideas page.
Thanks!
>
>
> Werner
>
>
> ==
>
>
> LilyPond is a music engraving program, devoted to producing the
> highest-quality shee
Han-Wen Nienhuys writes:
Hey,
> Every year, we go over the source code to update the copyright years
> that are found in the source headers. I propose to stop this.
+1
> Also note that many other projects (eg. git) seem to survive just fine
> without yearly exercise like this.
Yes. Of course,
Le lundi 13 février 2023 à 11:07 +0100, Han-Wen Nienhuys a écrit :
> Hi there,
>
> Every year, we go over the source code to update the copyright years
> that are found in the source headers. I propose to stop this.
>
> We started doing this because of the GNU standards which say
>
> [https://
Hi there,
Every year, we go over the source code to update the copyright years
that are found in the source headers. I propose to stop this.
We started doing this because of the GNU standards which say
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
but we aren't following th
