Re: branching stable/2.22?

[Han-Wen Nienhuys]

On Fri, Sep 11, 2020 at 7:08 PM Werner LEMBERG <wl@gnu.org> wrote:
>
>
> >> > I don't see that in the current stage of upheaval of both
> >> > internals and build system and infrastructure, there is a point
> >> > in freezing off some half-baked intermediate state that hasn't
> >> > seen significant exposure to extensive testing.
> >>
> >> +1  It's too early IMHO.  Let's wait at laest a month.
> >
> > To be clear here: You mean at least one month before starting a
> > freeze?
>
> Yes.  The build infrastructure is still not ok.  For example, if I
> delete a PDF file, say, `notation.pdf`, right now it gets *not*
> rebuilt!

There is a comment about this:

# Do not specify phony targets (pdf, html) as dependencies to avoid building the
# webdoc tree every time.

We can make this accurate so your pdf file gets rebuilt, but it comes
at the cost of always building the webdoc tree even if there is no
work to do. This adds 5 to 10 seconds to a null-build, so I think it's
not a good tradeoff.

The new documentation build has much more accurate dependency
tracking, so if you want to rebuild notation.pdf, you can just say so:

  make out=www out-www/en/notation.pdf

> Similarly, if I change a documentation string in an SCM file
> like `define-markup-commands.scm`, the documentation doesn't get
> rebuilt, either.

I can look at reintroducing the SCM -> texi dependencies.

>  I consider this fundamental flaws.

I disagree. These flaws might be a bother for developers, but
branching stable/2.22 is about not having user-visible regressions of
lilypond itself, relative to 2.20, which has nothing to do with how
developers experience working on lilypond.

> > This is not my proposal anymore to just branch, but Han-Wen's idea of
> > having a freeze of 3-4 weeks before branching.
>
> For me, a freeze can only start if we agree that nothing fundamental
> has to be changed or added.  IMHO, we are far away from such a state.

Could you enumerate the issues you think are fundamental?

--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen