CVS directory cleanups

git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@96 91ce42f0-d328-0410-95d8-f526ca767f89

diff --git a/bacula/CheckList b/bacula/CheckList
new file mode 100644 (file)
index 0000000..17c8fd2
--- /dev/null
+++ b/bacula/CheckList
@@ -0,0 +1,16 @@
+
+             Release Check List
+
+- Build it on Win32
+- Build it on Sun
+- Build FD on Irix
+- Update ChangeLog
+- Make new .pdf manual
+- Do a cvs commit
+- Do a cvs -q export -D now -d bacula-1.nn bacula
+- Build new bacula-1.nn to ensure everything is committed
+- Write ReleaseNotes
+- If everything is good
+- cvs -q tag Release_1_nn
+- rm -rf bacula-1.nn
+- cvs -q export -r Release_1_nn -d bacula-1.nn bacula

diff --git a/bacula/README b/bacula/README
index ba488c6bd779a3ade5fd0828c21ad676648701b5..d028fe86f65cdff32bf8358d58c129a44bda0c2e 100644 (file)
--- a/bacula/README
+++ b/bacula/README
@@ -5,7 +5,7 @@ numbering conventions, but rather one that I started in
 another user was 1.0, each modified source code release then
 gets a new minor release (1.1, ...) as well as a date.  Each
 major change in the software -- e.g.  new tape format will
-have the major release number incremented.
+normally have the major release number incremented.
 
 Your best bet for getting Bacula up and running is to read
 the manual, which can be found in
@@ -34,8 +34,8 @@ Build Bacula
 
    make
 
-   There should be no errors.  The most likely source of
-   errors will probably come in the src/stored directory
-   in time.c or dev.c.  There may also be problems in
-   lib/signal.c as I currently pull in all Linux signals,
-   some of which may not be available on your system.
+   If you are doing a port, there should be no errors.  The most
+   likely source of errors will probably come in the src/stored
+   directory in time.c or dev.c.  There may also be problems in
+   lib/signal.c as I currently pull in all Linux signals, some of
+   which may not be available on your system.