Hendrik Boom <hend...@topoi.pooq.com> writes: > On Sat, May 20, 2023 at 01:06:12PM +0100, RL wrote: >> James Addison <j...@jp-hosting.net> writes: >> >> > (someone who knows more may correct me, but I think it would be great to >> > have >> > the package available for install using apt in addition to the website) >> >> Interesting idea, but who would use it - won't a release-notes package >> always be a whole release out of date? > > It would mean that the realease-notes package on your system > would always match the release on your system.
Can i ask why that is beneficial: how it would make your life better? i know you are not saying the website version is going away, but i'm afraid i don't understand the use-case for a packaged version. Maybe i am missing out on something. For me, the value of release-notes is to know what things need to be thought about as part of the upgrade. Especially things that need to happen before the dist-upgrade, such as 'do not upgrade an i386 system unless it is really i586', or 'this package is going away': sometimes, i wouldnt start the upgrade until i knew what was replacing removed packages with (see the current warning about gnome and orca for example). I also wonder how practical it is to achieve. At the moment, bookworm is frozen, and release-notes are work-in-progress - there are still open bugs with draft text and open merge-requests. Is it realistic for everything in release-notes to be finished (including translations) and for someone to upload a package ensure it makes it into bookworm debian during the full freeze before the release happens? I suppose you envision bookworm releasing with a best-efforts version, and re-uploading as part of point releases? If it is a package, shouldnt it be available in man/roff format so it is always readable from a text console?
