This document covers the various areas you need to know to release RSBAC :)

mr is the release tool (svn:svn.rsbac.org/rsbac-misc/mkrelease). Use it to make tarballs and stuff to release :) <code> -a, –archive Create release archive in DESTDIR -d, –diff 24|26|ALL Shows a diff with trunk -rd, –rdiff Shows a diff between RSBAC code of 2.4 and 2.6 kernels -c, –compile utils|24|26|ALL Test compilation -t, –tag Create tags SVN side -s, –sign Signs and hash packages in DESTDIR -l, –clean Clean temporary files after execution -h, –help This cruft </code> You should first test kernel&utils compilation, then check the rdiff (if there is a difference between 2.4 and 2.6 common code, we have a prob), and the diff (its a smart diff, will only show RSBAC diff which are not in common code, with kernel trunk). This will also check that diffs are only rsbac related and not some kernel merge error. Read and check it as much as humanely possible in a decent time. Make the release with -a -s (and -l to clean up) Don't forget to check the packages created, upload them to the release server and make a tag with -t (or by hand) before it's too late :) Note: 2.4 support is deprecated and the tool does not make 2.4 kernels by default ==== Versions ==== Bump RSBAC admin tools versions: * main/libs/Makefile * main/tools/Makefile * main/tools/src/scripts/rsbac_*menu * main/headers/rsbac/types.h * main/tools/Changes * debian/* Bump kernel version: * include/rsbac/types.h, both kernels * Documentation/rsbac/Changes, both kernels