Hi folks,

First, a clarification of one of my emails from yesterday:

The code _freeze_ is now lifted/thawed.  I was running on fumes when I
composed that message.  (And I'm running on them again tonight, but also
greatly relived to finally have the 1.25 release out.)

Speaking of the new release, over a dozen distributors have packaged it
already, within 24 hours of upload.  A major of these appear to be
auto-monitoring the GNU FTP site, since they had their packages out
before I even sent the release announcement.

According to repology dot org, here are our sprint champions:

* aerynOS
* CRUX (3.8)
* Cygwin
* Debian (unstable)
* Devuan (unstable)
* Exherbo
* Homebrew
* KaOS ("Build", their rolling/unstable stream, I guess)
* openmamba
* Slackware
* stal/IX (I wonder if this distro has an aggressive purge policy)
* starkOS
* T2 SDE
* Termux
* Vylen Linux (et voilá!)

Fedora and OpenSUSE are seldom quick to package new groffs, so I
wouldn't expect them terribly soon--but they get there eventually.

Regarding the thawed code freeze, I've pushed my first batch of feature
changes.  I've had these in queue in a private branch, and still have
some more to cherry-pick and finalize with change logs and such.

Here are the first NEWS items for groff 1.26.

VERSION next
============

troff
-----

*  The `ne` request no longer performs an operation if it is given an
   invalid argument.  This change is inconsistent with AT&T troff but
   more consistent with general *roff syntax.

*  The `shift` request no longer performs an operation if it is given an
   invalid argument.

*  A new read-only register `.sv` reports the amount of vertical space
   saved by the most recent `sv` request, if it has not yet been output
   with the `os` request.

*  The `pev` request now reports the environment's modified glyph height
   and slant, as applicable; and its selected control and no-break
   control characters.

*  The formatter now emits a warning in category "style" if -crementing
   interpolation (such as `\n+[myreg]` or `\n-[count]`) is (uselessly)
   applied to a non-auto-crementing register.

Comments?  Objections?

Regards,
Branden

Attachment: signature.asc
Description: PGP signature

Reply via email to