$Id$

			README.developer for MBSE BBS

This file is only available on CVS, not in the distribution. This file will
hold information about CVS tags, scheduled releases and other info for
development only. There are no secrets in this file because it's public
available.



	CVS tags.

mbsebbs-0_33_17		17-Aug-2001 Initial CVS import by Ken.
mbsebbs-0_33_18_current	25-Aug-2001 Upgraded to 0.33.18 current development.
mbsebbs-0_33_18_final	02-Nov-2001 Version 0.33.18 released.
mbsebbs-0_33_19_current 02-Nov-2001 Start 0.33.19 current development.
mbsebbs-0_33_19_final	10-Feb-2002 Version 0.33.19 released.
mbsebbs-0_33_20_current	10-Feb-2002 Start 0.33.20 current development.
mbsebbs-0_33_20_final	04-Jun-2002 Version 0.33.20 finished (not released).
mbsebbs-0_33_21_release	04-Jun-2002 Version 0.33.21 release.
mbsebbs-0_35_01_current 05-Jun-2002 Start 0.35.01 development.
mbsebbs-0_36_00_release 26-Dec-2002 Version 0.36.00 release.
mbsebbs-0_37_00_current 26-Dec-2002 Start version 0.37 development.
mbsebbs-0_38_00_release 03-Oct-2003 Version 0.38.00 release.
mbsebbs-0_39_00_current 09-Oct-2003 Start version 0.39 development.
mbsebbs-0_50_00_release 09-Feb-2004 Version 0.50.0 release.


	CVS usage.

This will only work for registered MBSE developers. Replace username with your
sourceforge's username. To initialize your account on the sourceforge cvs 
server do:

ssh username@cvs.sourceforge.net

This command will fail but creates your homedirectory on the sourceforge cvs
server.

Set the following two variables (and add them to .profile):

export CVS_RSH=ssh
export CVSROOT=username@cvs.mbse.sourceforge.net:/cvsroot/mbse

Install the sources with the followin command:

cvs -dusername@cvs.mbse.sourceforge.net:/cvsroot/mbse co mbsebbs

That will create the directory mbsebbs with all subdirectories. When you made
some changes you can commit these from within the directory mbsebbs with:

cvs ci -m "Description of your changes"

To get a fresh source with changes of other developers do:

cd mbsebbs
cvs update


Michiel.