From bca390b9c0093b14639ec7e28c574e38d62b98b8 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Thu, 15 Aug 2002 07:31:23 +0000 Subject: [PATCH] CVS directory cleanups git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@96 91ce42f0-d328-0410-95d8-f526ca767f89 --- bacula/CheckList | 16 ++++++++++++++++ bacula/README | 12 ++++++------ 2 files changed, 22 insertions(+), 6 deletions(-) create mode 100644 bacula/CheckList diff --git a/bacula/CheckList b/bacula/CheckList new file mode 100644 index 0000000000..17c8fd2d15 --- /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 ba488c6bd7..d028fe86f6 100644 --- 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. -- 2.39.5