This page provides some details about the process of a new grml release. This is mika's todo- and checklist:

  • fix any outstanding release stopper issues
  • are there any outstanding issues (if so: fix) from:
  • make sure kernel, udev, initramfs-tools and live-initramfs are in a good shape
  • get sources for all flavours of the release (this step has to be done before uploading any stuff, especially important since is b0rken) →
for f in * ; do chroot $f/grml_chroot grep-status -F Status -e '^install ok installed$' -s Status,Package,Version,Source > "${f}_grep-status" ; done
perl get_sources grml_$ID/grml_$ID.yaml
perl gen_index
./ | grep -v 'does not exist'  | grep -v 'is the same'
  • copy grml-testing repository to grml-stable and store old grml-stable as grml-$ID
  • provide terminalserver files for new release
  • final checks:
    • boot all flavours inside virtualbox/kvm/…, on physical hardware,… including booting with different bootoptions
    • install grml to usb pen using grml2usb
    • execute grml2hd
    • run 'm-a a-i drbd8' (is it possible to compile kernel modules in live system?)
    • run 'grml-x wm-ng' (is the desktop ok?)
    • test sound (soundtest)
  • provide rc1 of all flavours:
    • sign sha1 of ISO files with gpg
    • push ISOs to mirror
  • update (release stuff, check for deprecated stuff)
  • update startpage, download, screenshots, static_bottom, news, changelogs, roadmap, kernel, rss, search

Repeat all the steps if necessary (rc1→rc2). Finally rerun all the above steps for the stable release and provide rc1→stable change information.

release.txt · Last modified: 2011/10/13 23:55 (external edit)
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Grml homepage Driven by DokuWiki