1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
Release Check List
Assume release is in bacula/base bacula/gui bacula/docs bacula/rescue
- Build it for Win32 and on Win64
# No longer done
# - Build it on Solaris and run regression tests
# - Build it on FreeBSD and run regression tests
- Update ChangeLog (add release date)
- Update ReleaeNotes
- Do a svn commit
# ./makerel <branch-name> <local-branch-source-dir> <release>
- Run ./makerel Branch-2.0 branch-2.0 2.0.x
- Run the regression tests on the new bacula
directory that is created. Run regression on
Linux.
- Run the production version over night in production.
- Manually test Win32 version
(with Robert's work, it is now possible to run the
Regression scripts).
- Write final ReleaseNotes
- If everything is good
- cd bacula
# The below needs to be updated more
- Run
cd base
svn update
cd ../gui
svn update
cd ../docs
svn update
cd manual
make tex
latex bacula.tex
(make sure the above finishes. If it stops and asks
what to do, correct the problem).
cd ..
cd ../rescue
svn update
cd ..
./makerel base 2.0.x
./makeguirel gui 2.0.x
./makedocsrel docs 2.0.x
./makerescuerel rescue 2.0.x
cd base/win32
make
cp release/winbacula-2.0.x.exe $HOME/bacula
cd $HOME/bacula
./sign winbacula-2.0.x.exe
- Upload everything to appropriate part of Source Forge
and release it. I use releaseforge
- After releasing everything.
- Either download everything and compare the signatures,
or simply check the upload sizes of everything.
- cd docs/manual
make
- Upload new release doc to web site.
Upload bacula.pdf to web site.
- Update news on web site.
|
