Hi, Ben Hutchings <email@example.com> (2017-03-30): > Please go ahead. There may be some users that set module options at > installation time and don't want them set in the installed system. But > they are likely to be outnumbered by those who do want them set. If > the installer can boot with those module options then the installed > system very likely can too. Thanks for weighing in. Phil, let's do that; note: we have a couple of days at least before Stretch RC 3 but the sooner it gets uploaded, the better. > > At least, are there any plans to keep the list of hardcoded things > > uptodate? > > This is a good point. Is there a list of things to check during each > release cycle? There isn't yet (at least that I know of), but there should be. There are a list codenames in various components (if not only src:d-i), bits for the website, probably the installation guide etc. But it would be nice if we could just automate doing so on a regular fashion, e.g. using some cronjob on dillon (see also detecting missing git pushes for branches/tags). I'll probably deal with this specific bit, but documentation could be added to the wiki I suppose. Wiki pages should probably get a review at some point, too, but that's another topic. KiBi.
Description: Digital signature