[PD-cvs] SF.net SVN: pure-data: [9305] tags/README.txt

[zmoelnig at users.sourceforge.net]

Revision: 9305
          http://pure-data.svn.sourceforge.net/pure-data/?rev=9305&view=rev
Author:   zmoelnig
Date:     2008-02-07 07:25:13 -0800 (Thu, 07 Feb 2008)

Log Message:
-----------
added a README.txt

Added Paths:
-----------
    tags/README.txt

Added: tags/README.txt
===================================================================
--- tags/README.txt	                        (rev 0)
+++ tags/README.txt	2008-02-07 15:25:13 UTC (rev 9305)
@@ -0,0 +1,26 @@
+this is the tags/ directory of the pure-data repository
+
+since this directory was initially created in the migration from cvs to svn,
+it is a bit unorganized.
+there is a special folder: "/tags/by-author" which mainly holds the initial 
+CVS-imports. (there could be done some more cleanup in these)
+
+the "TODO" folder holds all the CVS-tags which still need a bit of 
+reorganisation.
+
+for the future, i propose that
+ whenever you create a branch of something, you put it into a subfolder:
+examples:
+ pd-vanilla:	"/tags/pd/v0-41-0"
+ pd-extended:	"/tags/pd-extended/v0-39-0"
+ zexy: 		"/tags/externals/zexy/zexy-2-0"
+
+
+in general, it might be a good idea to name the actual branch to something 
+meaningful, where people will immediately understand that this is a branch.
+e.g. using your username as branch might be a bad choice: 
+	BAD:  "/tags/externals/iem16/zmoelnig/"
+probably it is a good idea to repeat the module's name, with some branch-
+information suffixed:
+	GOOD: "/tags/externals/iem16/iem16-v1.0/"
+


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.