if you look at /data/delta/OpenAFS-(branchname) on grand.central.org you can see what other branch prefix is used, for each branch. i promise to start keeping track of this in a file.
+There's an expectation that you review code you commit, or, if you're committing your own code, you have other(s) review it. In the case of things which are obvious, you don't need to worry about this.
+
+Please fill in the template for CVS commits as completely as possible, including license and RT ticket reference, if any.
+
+Additional tools: ~shadow/getdelta (also getdelta-devel15 and getdelta-stable14) will fetch all patch pieces of a delta.
+
+Releases and prereleases get tagged on their respective branches, please tag branchpoints when branching with BP-branchname (e.g. 1\_4\_x branch had moved past 1.4.5 but to release 1.4.6 with security fixes only we tagged a brachpoint at 1.4.5, branched and put only the 1.4.6 patches on it, then tagged)
+
+To make a release, on grand, /usr/local/sbin/make\_release repo tag version (previous tag) - generally invoked as e.g. make\_release openafs openafs-stable-1\_4\_5 openafs-1.4.5 openafs-stable-1\_4\_4
+
+To build web pages for a release, /usr/local/sbin/make\_www\_release (version) (path)
+
+path is where to write the web pages, it expects (path)/release/(version) to exist as a directory. Those files can be committed on grand in /data/htdocs/openafs/release/(version), except release/(version)/index.html which should be committed as /data/htdocs/openafs/release/openafs-(version).html
+
-- [[DerrickBrashear]] - 09 Jan 2008