Re: groff 1.24 release goals and gates

Hi Peter,

At 2025-11-15T15:00:29-0500, Peter Schaffter wrote:
> On Sat, Nov 15, 2025, G. Branden Robinson wrote:
> > I think groff 1.24.0.rc1 is finally coming into view.
> 
> Just the release candidate, or the actual release?

Just the release candidate; I don't have the courage to push a final
release with _no_ release candidates, and we haven't had any for 1.24.

That said, if RC1 is well received and raises no issues demanding a code
change, I see no reason not to go to final release after that.  (That's
kind of my definition of a "release candidate"--if it builds and runs
and no defects arise warranting code changes, it's a successful
"candidate".)

What I took away from the 1.22.4 and 1.23.0 release cycles shows was
that 2 weeks is about as long as we need for RC feedback.  I remember
being frustrated that holding the RC window open for a third week didn't
seem to accomplish much.

It's my first time doing this officially for groff, of course.  I'm open
to feedback or suggestions about release management.

Regards,
Branden

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmkY/o4ACgkQ0Z6cfXEm
bc5ffhAAlS6rR3kGvb9VeMmWLlONWrqhUuyN6aVEK8sqnc0iGLzWHIgdJKTUfteT
LfjAhLtoGa87PXU+hozG66eBRC55FHnuAfkcJL2snxn5O+2kPhA6aB/3+R/9h15C
mAmos5YnWdUTL09twoOD4PwYp+s+/lqVmkwu67CfTK43gqwHDxfOrhIZdcJoeRJ1
tGO8t1LUwXybQbYsmAWPiOUO4D22ouOBDMV2EA2pvQcSpps8sqXw9X+8ANCbk3jl
zc0d7ODcz2F8MN9cWCx7eF1xkuL4qqFdsy19LEDBBbwm9h4S5zI20I4AUs88vgjZ
btZGGdH+5olUJDKbsKCEnrsEsY9L/Cab1PApLI8ln5m7Ld4V6YXhKiQHencBiChu
hxdXolzxpGOhOKdhKzhezdKap1gV6Hcu3mPSMt09EHSqw+mbNpYs8tBmnQJcE92p
UTOqbLr1B8GJ2Au8KXcro7ugrGfieIJglysY5WjW2D5JzeeqMLaQ7AoxEtnA/FFN
4PdLqyV+0cafdhdbG18xuZvimtH6EgEs3tgvSmce6RSiHbYUghM4TUHvhoy5tAkm
F6puhAHWxBf82CEQ4W4SqmTRUgT8/QKwEK4l8T6BdggOywHIiME7pJd32OnMRGuv
19IAn+qvf9lHIWWQ9HDhRcP+QwKol6yZbR+AQ8hOJrb91UMhWcU=
=BYz0
-----END PGP SIGNATURE-----