Is there any plan for how the web site update will be handled for sarge's release? Besides just switching the names and links to sarge, I've been looking at what parts of the web site will need updating for the new installer and other missing bits. These include: - distrib/floppyinst: needs a thurough rewrite for d-i, could probably be replaced with a pointer to the same info in the sarge installation howto (part of the sarge installation manual) - CD/netinst: official netinst images for stable will be available; the old images were not official and the location has changed - CD/jigdo: probable url change - sarge/installmanual: doesn't exist. One possibility is to link to the sarge install manual in the debian archive on a mirror, which is updated whenever the images are updated. I don't know how the woody install manual is imported into the web site so maybe however it is manage is better. - sarge/: missing credits, errata, releasenotes, reportingbugs pages that all exist for woody. Also the sarge/index.wml itself will need some extensive changes. - doc/FAQ: needs a read-through and some updates for d-i. For example, section 2.2 points users to directories that have been renamed for d-i. Some of these involve a lot of rewriting and should not go live until sarge is released. Any suggestions on a good way to handle that? A branch in cvs does not seem very workable. Maybe someone can do some wml magic to select different paragraphs depending on whether release/info has current_release_name set to woody or sarge? -- see shy jo
Attachment:
signature.asc
Description: Digital signature