On Fri, Feb 07, 2025 at 08:24:27PM -0600, G. Branden Robinson wrote:
> I feel it necessary to disclose that while getting 1.24 ready on the
> timetable Colin required for the Debian Trixie release freeze (about 8
> March) looked like a tight squeeze a couple of weeks ago, I now have
> no confidence that it can be met with anything more than a perfunctory
> rc1, and if we needed to roll an rc2 we'd be simply sunk.
> 
> Judging by past experience, an RC needs to percolate for 2-3 weeks, and
> after that there's little evidence that any further useful feedback
> about it comes in.
> 
> Absolutely everything would have to go right--and my maintainerly powers
> to upload things to GNU servers are as yet untested--and since the 27th
> something else has gone wrong, this time Savannah #66758.  Another
> change from last October has proven to have untoward and unintended
> consequences.  (This time it's a change to the mm package's debugging
> interface of all things.  With any luck it's just a dumb syntax error.)

Yes, I'm pretty sure it's just that.  I attached a suggested patch there
(though I didn't do any more sophisticated analysis, such as e.g.
viewing the resulting document ...).

> This is somewhat frustrating but it's better to find these issues before
> making an RC, let alone a final release.  Better now than later.  Thanks
> go to Dave and Deri for giving the master branch thrashings that exposed
> issues that existing automated tests did not.
> 
> So while I'll continue to work toward a release candidate and final
> release as soon as is feasible, I think that's going to be on the other
> side of the Debian toolchain/central infrastructure freeze deadline that
> Colin asked me to meet if I wanted to see 1.24 in Trixie.
> 
> It seems that a curse afflicts the synchronization of the Debian and
> groff release schedules.  (Maybe the curse bears my name.)

Thanks for the update.  If it's in time, I'll do what I can.  Otherwise,
I hope 1.24 can be the start of a practice of doing smaller and more
frequent groff releases, with which this sort of thing would be much
less of a problem.

-- 
Colin Watson (he/him)                              [cjwat...@debian.org]

Reply via email to