Re: Move u2f-devd into base?

David Chisnall <theraven_at_FreeBSD.org> wrote on
Date: Mon, 08 Jan 2024 17:12:06 UTC :

> On 8 Jan 2024, at 16:30, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote:
> > 
> > So it should be in ports to adapt for latest products more quickly than
> > in base, I think.
> 
> We push out a new release of each of the -STABLE branches every 6 months

https://www.freebsd.org/releases/ reports (mixing "Most Recent" and
"Prior Releases - EOL" lines for 13.x):

    • Release 13.2 (April 11, 2023) Announcement : Release Notes : Installation Instructions : Hardware Compatibility List : Readme : Errata : Signed Checksums
. . .
    • 13.1 (May 16, 2022) Announcement : Release Notes : Installation Instructions : Hardware Compatibility List : Readme : Errata : Signed Checksums
    • 13.0 (April 13, 2021) Announcement : Release Notes : Installation Instructions : Hardware Compatibility List : Readme : Errata : Signed Checksums

and for the end of the 12.x releases:

    • 12.4 (December 5, 2022) Announcement : Release Notes : Installation Instructions : Hardware Compatibility List : Readme : Errata : Signed Checksums
    • 12.3 (December 7, 2021) Announcement : Release Notes : Installation Instructions : Hardware Compatibility List : Readme : Errata : Signed Checksums

Looks more like around a year for each separate stable/?? to me.

> and can do ENs if a product ships and becomes popular in under six months. This shouldn’t be a reason to not do things in the base system.
> 
> Streamlining the process for ENs (automating them so that there’s a simple flow from review request for a commit on a stable branch to generating the binaries and sending out the announcement) would help a lot and would almost certainly make Colin happier about his workload.

===
Mark Millard
marklmi at yahoo.com