[fusionregistry commit] r19 - wiki
codesite...@google.com
Date: Sun Aug 3 22:10:08 2008
New Revision: 19
Added:
wiki/VersionControl.wiki
Log:
Created wiki page through web user interface.
Added: wiki/VersionControl.wiki
==============================================================================
--- (empty file)
+++ wiki/VersionControl.wiki Sun Aug 3 22:10:08 2008
@@ -0,0 +1,101 @@
+#labels Phase-Implementation
+=Version Control=
+Fusion Registry GPL uses subversion (SVN) for version control. This page covers the following topics:
+
+==Beta / Release Candidate / Final==
+There is no general practice that requires a certain number or path of releases (Beta -> RC -> Final). A release could go directly to RC, or directly to Final (although not suggested). There may only be one Beta or RC releases, there may be many. It will be determined by the state of the release at the time. If a Beta release contains a lot of issues and is highly likely to have more, or features are not yet complete, there will probably be another Beta release before a RC release.
+
+Beta releases are incremental code releases, all major functionality might not be complete, and there are either known issues in the code, or it is not fully tested. Beta releases are meant to help identify problems and give feedback as to the direction of the release, not for use in a live production site.
+
+Release Candidate (RC) releases are production ready code, all features are complete, any known issues are resolved, and no new features will be added to this version. A RC release is a preview of the final version and is used to shake out any remaining issues not yet identified. If there are no further issues discovered a final release is made.
+
+
+==Checkout Repository==
+The repository can be checked out with the command:
+{{{
+svn co https://url/svn/trunk fusionregistry
+}}}
+See the branching strategy below if you want to checkout a particular branch or tag of the repository.
+
+
+==Subversion Config Settings==
+You’ll need to add a couple of config settings to your SVN config file. In Windows your config file is located at:
+{{{
+C:\Documents and Settings\YourUserName\Application Data\Subversion\config
+}}}
+
+For Unix/Mac OS X:
+{{{
+~/.subversion/config
+}}}
+
+===Enable auto-props===
+Open up your SVN config file and locate `[`miscellany`]` and enable-auto-props. If they exist, make sure that they are uncommented (remove # from beginning of line), otherwise add them. The line should look like:
+{{{
+[miscellany]
+enable-auto-props = yes
+}}}
+
+===Configure auto-props===
+Locate the section `[`auto-props`]`. If it doesn’t exist, add it. If it already exists but is commented out, simply uncomment it. Add or modify the following entries below `[`auto-props`]`:
+{{{
+*.sh = svn:eol-style=native;svn:executable
+*.txt = svn:eol-style=native;svn:keywords=Id
+*.css = svn:eol-style=native
+*.xml = svn:eol-style=native
+*.html = svn:eol-style=native
+*.htm = svn:eol-style=native
+*.js = svn:eol-style=native
+*.php = svn:eol-style=native;svn:keywords=Id
+}}}
+
+
+==Branching Strategy==
+The SVN repository contains the following folder structure:
+
+{{{
+trunk/
+
+branches/
+ bugfix_3_0_x/
+ bugfix_3_1_x/
+ dev_feature/
+
+tags/
+ rel_3_0_0/
+ rel_3_0_1_b1/
+ rel_3_0_1_rc1/
+ rel_3_0_1/
+ rel_3_0_2/
+ rel_3_1_0/
+
+tools/
+
+wiki/
+}}}
+
+===trunk===
+This is the place where most of the actual development happens. Any snapshot of the trunk you may check out, is a snapshot that is not regarded as being stable and usable. It is not recommended to use the trunk version for any production use.
+
+===branches===
+There are two types of branches, stable bugfix and temporary development. When the trunk is about to start work on the next major release it is copied to a stable bugfix branch, which is denoted by the prefix 'bugfix`_`' followed by the major and minor version numbers, for example 'bugfix_3_0_x'. Any further bug fixes for that version are committed to that version's branch. When bug fix releases are tagged they are also merged back into the mainline trunk.
+
+The other types of branches are temporary development branches denoted by the prefix 'dev`_`' followed by a short name to reflect the feature or purpose of the branch. These branches are usually short lived and are meant for major modifications that would otherwise render the trunk version unusable.
+
+===tags===
+Released versions will be tagged with the following scheme, 'rel`_`' followed by version number, then optionally the notation of being a beta or release candidate. For example, 'rel_3_0_0' is version 3.0.0 final; 'rel_3_0_1_b1' is version 3.0.1 beta 1; 'rel_3_0_1_rc1' is version 3.0.1 release candidate 1. Tags should be treated as 'read-only', no commits should ever be done on tags/.
+
+Beta releases are not for use in a live production site, they are mainly used to test the software and identify problems, and support will be best effort. Release candidate releases can be used in a live production site and are supported; they are generally stable with all known major issues resolved.
+
+===tools===
+Handy development tools/scripts.
+
+===wiki===
+Contains all the project wiki pages.
+
+==Locks==
+The only element that requires a lock is the 'ipb_skin-fusionregistry.xml.gz' file because of the large binary format of the skin export. It is general practice to request the lock on the skin file before you start making changes to the skin in your development forum. When you are done making skin changes, export the skin and commit the new file releasing the lock. This is to prevent people's skin changes from being lost.
+
+
+==Submitting Patches==
+If you would like to contribute to the project please use the [http://forums.fusionscripts.com/index.php?showforum=34 development forum] to submit new code or patches. The core developers will evaluate the patches and commit them to the repository.
\ No newline at end of file