Re: [RFC] Use GitLab Milestones

[Carl Sorensen]

On Tue, Jun 23, 2020 at 2:25 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>
> Am Dienstag, den 23.06.2020, 14:11 -0600 schrieb Carl Sorensen:
<snip.
>
> > Accepted: the Bug Squad added it, or reviewed the item.
> > Started: a contributor is working on a fix. Owner should change to be
> > this contributor.
> >
> > Closed issues:
> >
> > Invalid: issue should not have been added in the current state.
> > Duplicate: issue already exists in the tracker.
> > Fixed: a contributor claims to have fixed the bug. The Bug Squad
> > should check the fix with the next official binary release (not by
> > compiling the source from git). Owner should be set to that
> > contributor.
> > Verified: Bug Squad has confirmed that the issue is closed. This means
> > that nobody should ever need look at the report again – if there is
> > any information in the issue that should be kept, open a new issue for
> > that info.
>
> Which one of those would apply to an issue like
> https://gitlab.com/lilypond/lilypond/-/issues/6000 ?
>

My guess is that it should be Accepted.  It's a real issue, not an
imaginary one.

I believe that the proper fix for this issue is to make our
configuration check for fontforge see whether python scripting is
enabled, and if not, to generate a message informing the user of that
fact.

I don't think it's fixed, because it's easy to set up a system with
FontForge not having python scripting enabled.

But that's just my opinion.

Thanks,

Carl