Read Me

struts timeEntry subversion file organization
-----------------------------------------------------------------

Copyright 2006 Steve Brettschneider

This file is part of struts timeEntry.

struts timeEntry is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

struts timeEntry is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with struts timeEntry; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA

-----------------------------------------------------------------

This file describes the file layout of the subversion repository
for struts timeEntry on the sourceforge.net servers.  Please
direct questions/concerns to steveb8082@users.sourceforge.net.

Last updated: May 18th, 2006

-----------------------------------------------------------------

The root directory of the repository has three subdirectories:
branches, tags and trunk.  This is a typical directory layout
for subversion repositories.

trunk - The trunk subirectory is where all main development
should take place.  When we reach a point in time where we feel
we may be ready for a release, we will create a branch for that
release.

branches - Once we feel we might be ready for a release, a sub-
directory is created off of this directory for the release.  It
will take the form of major.minor (example: /branches/1.0).
Code in this branch will go through a QA process until we feel
it is ready for official release.  When that is done,  will
create a branch for that finalization.  Bug-fix releases will
branched from branches in this directory.  (example: we might
create a copy of /branches/1.0 to /branches/1.1).  Rebranching
from /trunk will only occur for major releases.

tags - When a release occurs, a branch is put in this directory
that is considered FINAL.  No changes will be permitted to
files/folders in the branches in this area.  As an example,
when the code in /branches/1.0 is ready for release, it will
be branched to /tags/release-1.0.  The code in /tags/release-1.0
will never be changed.  The code in /branches/1.0 will be copied
to /branches/1.1 to be modified for bug fixes.