groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: groff maintainership, release, and blockers


From: Bertrand Garrigues
Subject: Re: groff maintainership, release, and blockers
Date: Mon, 29 Aug 2022 00:34:18 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)

Hi Ingo,

On Sat, Aug 27 2022 at 12:49:05 PM, Ingo Schwarze <schwarze@usta.de> wrote:
> Bertrand Garrigues via wrote on Fri, Aug 26, 2022 at 11:53:07PM +0200:
[...]
>> Could you please detail here what is your list of blockers that you
>> think must be absolutely fixed before the official 1.23.0 release?
>
> I cannot give a final list off the top of my head because i am aware
> of several candiadates of regressions that require analysis.
>
> Are you planning to move towards an RC during the next two to three
> weeks?  In that case, i should probably priotize triage over fixing
> which i usually avoid (if possible) because it increases the total
> working time consumed.  But it would speed up drafting a list of
> potential issues that might be worth fixing before release.

Yes it was my intention was to push the rc2 as soon as possible, as the
current state of groff looked good enough,

> I recommend investigating this one before RC2, if feasible:

OK,

> #62918 Wrong GhostScript version reported during build
> There remains a regression in man(7) .EX/.EE which i will report ASAP.

as Branden said he will fix his 1st commit we'll wait for his fix before
the generation of rc2.

> Even though this is documentation only, i recommend resolving it before
> RC3 because switching back and forth in terminology in three consecutive
> releases could be regarded as awkward:
>
> #62816 rename the \& escape...again

I've marked this one for 1.23.0 in the bug tracker.

Regards,

Bertrand



reply via email to

[Prev in Thread] Current Thread [Next in Thread]