On 04.06.25 22:42, Edward Sanford Sutton, III wrote:
Please consider what breaks, when, and if support breaks then make
sure it is being well documented in appropriate places (errata, src/
UPDATING, ports/UPDATING, likely mailing list HEADS UP, etc.). Not sure
why but it seems like developers sometimes don't get things into release
notes that are issues which really should be documented there too. Man
pages may benefit from bringing attention to user facing breaking
changes and/or mentioning of the instability.
Actually, this, and more.
There are people with Wifi-only Internet access.
If their Wifi stack breaks, they can't download a patch; any remedy has
to be already in place.
I guess that means whatever you do, you need to make sure that Wifi
upgrades can be rolled back without doing downloads.
Maybe even keep the old ABI around so old drivers continue to work, so
users can alternate between drivers.
Might be useful for all kinds of A/B testing, too.
Just my thoughts.
Regards,
Jo
