Changes between Version 6 and Version 7 of UfoRevisionControl

Timestamp:

Mar 18, 2011, 11:59:33 PM (14 years ago)

Author:

Suren A. Chilingaryan

Comment:

--

UfoRevisionControl

@@ -1 @@
-= Repositories =
+= UFO Revision Control =
 
-There were some problems with integration of Git repositories into Trac. Therefore, I decided to install bazaar as a revision
-control system: http://bazaar.canonical.com/en/. The good documentation on bazaar commands is available here:
-http://doc.bazaar.canonical.com/bzr.2.2/en/
+Bazaar is an official revision control system for UFO.
+ * [http://bazaar.canonical.com/en/ Bazaar Official Web Site]
+ * [http://doc.bazaar.canonical.com/bzr.2.2/en/ Bazaar Official Documentation]
 
-I have installed the main repository for framework development. It is
-accessible with the following bazaar URL:
-{{{ 
-  bzr+ssh://user@ufo.kit.edu/framework 
-}}}
-
-You can create new branches with the following command. These branches will be writable by creator only, but accessible for everybody else. Changes to these branches will immediately appear in the Trac [http://ufo.kit.edu/ufo/browser source browser].
-{{{
-  bzr init bzr+ssh://user@ufo.kit.edu/framework/branch1
-}}}
-
-
-After branch initialization you can create local repository. Just call 'bzr init' in root of the source folder. Files can be added with `bzr add` command and revision can be commited with `bzr commit -m some_comment`.
-This will work with local repository on your desktop computer. To submit a stable revision to the server, for public use, please issue:
-{{{
-  bzr push bzr+ssh://user@ufo.kit.edu/framework/branch1
-}}}
-
-Alternatively, it is possible to instruct bazaar to synchronize with the server after each commit. Just bind the local branch with the server using the following command:
-{{{
-  bzr bind bzr+ssh://user@ufo.kit.edu/framework/branch1
-}}}
-
-It is also possible to create a personal repository (for whatever reason). The access pattern will be the same: writable by creator and readable by everybody else. However, it will not automatically appear in Trac. The new repository should be first added through the Trac configuration page. The command:
-{{{
-  bzr init-repo bzr+ssh://user@ufo.kit.edu/repo1/
-}}}
-initializes the repository. Then, the branches can be created as usual:
-{{{
-  bzr init bzr+ssh://user@ufo.kit.edu/repo1/branch1
-}}}
-
-To get access, please, create a ticket specifying the desired login and attaching your public key.
-
-= Getting the source =
-In order to get the source out of the repository you should issue
+= Accessing Repositories =
+To get access to the bazaar repositories, please, create a ticket and attach your public SSH key. When access is granted, you
+can get the source out of the repository using following command:
 {{{
 bzr branch bzr+ssh://user@ufo.kit.edu/repo/branch
@@ -51 +18 @@
 {{{
 bzr branch bzr+ssh://user@ufo.kit.edu/vogelgesang/PyHST
+}}}
+
+= Public Repositories = 
+||= Repository =||= Description =||
+|| framework    || The stable version of UFO framework and support libraries. New versions are only accepted after thorough testing/code review. ||
+|| cmake        || CMake scripts to detect libraries you are maintaining. ||
+|| opencl       || Various CMake libraries required for UFO filters. ||
+|| <user_name>  || Development branches of all UFO related code belonging to the ''user_name''. ||
+
+== Publishing Source ==
+All the source code should first go to the user private repository. The repository is created with following command:
+{{{
+  bzr init-repo bzr+ssh://user_name@ufo.kit.edu/user_name/
+}}}
+The created repository will be only writable by its creator, but readable by all members of UFO project. The new repository will not automatically appear in Trac. It should be first added through the Trac configuration page. If you don't have administrative rights, you need to create a ticket.
+
+Then, the branches are created as follows (new branches will immediately appear in Trac):
+{{{
+  bzr init bzr+ssh://user_name@ufo.kit.edu/user_name/branch1
+}}}
+
+After branch initialization you can create local repository. Just call 'bzr init' in root of the source folder. Files can be added with `bzr add` command and revision can be commited with `bzr commit -m some_comment`.
+This will work with local repository on your desktop computer. To submit a revision to the server, for public use, please issue:
+{{{
+  bzr push bzr+ssh://user_name@ufo.kit.edu/user_name/branch1
+}}}
+
+Alternatively, it is possible to instruct bazaar to synchronize with the server after each commit. Just bind the local branch with the server using the following command:
+{{{
+  bzr bind bzr+ssh://user_name@ufo.kit.edu/user_name/branch1
+}}}
+
+= Publishing stable versions =
+After through testing, the maintainers of UFO subpackages can publish them in UFO main repository. It is
+accessible with the following bazaar URL:
+{{{ 
+  bzr+ssh://user@ufo.kit.edu/framework 
+}}}
+
+You can create new branches with the following command. These branches will be writable by creator only, but accessible for everybody else. Changes to these branches will immediately appear in the Trac [http://ufo.kit.edu/ufo/browser source browser].
+{{{
+  bzr init bzr+ssh://user@ufo.kit.edu/framework/branch1
 }}}