4 Assume release is in bacula/base bacula/gui bacula/docs bacula/rescue
7 - Build it on Solaris and run regression tests
8 - Build it on FreeBSD and run regression tests
9 - Update ChangeLog (add release date)
12 - Run ./makerel base 2.0.x
13 - Run the regression tests on the new bacula
14 directory that is created. Run regression on
15 Linux, Solaris, and Sun.
16 - Run the production version over night in production.
17 - Manually test Win32 version
18 (with Robert's work, it is now possible to run the
20 - Write final ReleaseNotes
21 - If everything is good
33 (make sure the above finishes. If it stops and asks
34 what to do, correct the problem).
40 ./makeguirel gui 2.0.x
41 ./makedocsrel docs 2.0.x
42 ./makerescuerel rescue 2.0.x
45 cp release/winbacula-2.0.x.exe $HOME/bacula
47 ./sign winbacula-2.0.x.exe
49 - Upload everything to appropriate part of Source Forge
50 and release it. I use releaseforge
51 - After releasing everything.
52 - Either download everything and compare the signatures,
53 or simply check the upload sizes of everything.
56 - Upload new release doc to web site.
57 Upload bacula.pdf to web site.