You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by cm...@apache.org on 2010/01/19 05:16:53 UTC
svn commit: r900658 - in /subversion/site:
publish/docs/hacking/release-process.html publish/release-process.html
site-map.txt
Author: cmpilato
Date: Tue Jan 19 04:16:53 2010
New Revision: 900658
URL: http://svn.apache.org/viewvc?rev=900658&view=rev
Log:
* site/publish/release-process.html
Move this...
* site/publish/docs/hacking/release-process.html
...to here.
* site/site-map.txt
Add some thoughts about reorgazing hacking et all into a single
structured document.
Added:
subversion/site/publish/docs/hacking/release-process.html
- copied, changed from r900550, subversion/site/publish/release-process.html
Removed:
subversion/site/publish/release-process.html
Modified:
subversion/site/site-map.txt
Copied: subversion/site/publish/docs/hacking/release-process.html (from r900550, subversion/site/publish/release-process.html)
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/hacking/release-process.html?p2=subversion/site/publish/docs/hacking/release-process.html&p1=subversion/site/publish/release-process.html&r1=900550&r2=900658&rev=900658&view=diff
==============================================================================
--- subversion/site/publish/release-process.html (original)
+++ subversion/site/publish/docs/hacking/release-process.html Tue Jan 19 04:16:53 2010
@@ -2,19 +2,11 @@
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>The Subversion Release Procedure</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<style type="text/css" media="screen">
- @import url("/style/site.css");
-</style>
</head>
<body>
-<!--#include virtual="/site-banner.html" -->
-<!--#include virtual="/site-nav.html" -->
-<div id="site-content">
-<!--#include virtual="/site-notice.html" -->
<h1 style="text-align: center;">The Subversion Release Procedure</h1>
@@ -541,7 +533,5 @@
</div> <!-- afterwards -->
-
-</div> <!-- #site-content -->
</body>
</html>
Modified: subversion/site/site-map.txt
URL: http://svn.apache.org/viewvc/subversion/site/site-map.txt?rev=900658&r1=900657&r2=900658&view=diff
==============================================================================
--- subversion/site/site-map.txt (original)
+++ subversion/site/site-map.txt Tue Jan 19 04:16:53 2010
@@ -40,9 +40,107 @@
TARGET PAGE
------ ----
SAO build-farm.html
- SAO hacking.html
REPO license-for-python-bindings.html
SAO mailing-lists.html
REPO repro-template.sh
SAO toctool.py
- REPO translating.html
+
+
+Exercise 2: HACKING (to use the obsolete, original name of this
+document) is in need of a major reorganization. The goal is a
+multi-page document that incorporates content from the existing
+hacking.html stuffs plus other developer-aimed stuff. The following
+is an attempt to map old content into a new structure.
+
+ <h2>The Basics</h2>
+ hacking.html:<h3>Participating in the community</h3>
+ hacking.html:<h3>Theory and documentation</h3>
+ hacking.html:<h3>Code to read</h3>
+ hacking.html:<h3>Directory layout</h3>
+ hacking.html:<h3>Documentation</h3>
+ hacking.html:<h4>Document Everything</h4>
+ hacking.html:<h4>Public API Documentation</h4>
+
+ <h2>Coding Conventions</h2>
+ hacking.html:<h3>Code modularity and interface visibility</h3>
+ hacking.html:<h3>Secure coding guidelines</h3>
+ hacking.html:<h3>Destruction of stacked resources</h3>
+ hacking.html:<h3>Coding style</h3>
+ hacking.html:<h3>Using page breaks</h3>
+ hacking.html:<h3>Error message conventions</h3>
+ hacking.html:<h3>Other conventions</h3>
+ hacking.html:<h3>APR pool usage conventions</h3>
+ hacking.html:<h3>APR status codes</h3>
+ hacking.html:<h3>Exception handling</h3>
+
+ <h2>Testing</h2>
+ hacking.html:<h3>Automated tests</h3>
+ hacking.html:<h3>Writing test cases before code</h3>
+
+ <h2>Debugging</h2>
+ hacking.html:<h3>Debugging the server</h3>
+ hacking.html:<h4>Debugging the DAV server</h4>
+ hacking.html:<h4>Debugging the ra_svn client and server, on Unix</h4>
+ hacking.html:<h3>Tracing network traffic</h3>
+ hacking.html:<h3>Tracking down memory leaks</h3>
+
+ <h2>Log Messages</h2>
+ hacking.html:<h3>Writing log messages</h3>
+ hacking.html:<h3>Crediting</h3>
+
+ <h2>Patches</h2>
+ hacking.html:<h3>Patch submission guidelines</h3>
+ hacking.html:<h4>The "Patch Manager" Role</h4>
+
+ <h2>Managing Issues</h2>
+ bugs.html (still living on Tigris.org)
+ hacking.html:<h3>Filing bugs / issues</h3>
+ hacking.html:<h3>Issue triage</h3>
+ hacking.html:<h3>Commit access</h3>
+ hacking.html:<h4>How full commit access is granted</h4>
+ hacking.html:<h4>How partial commit access is granted</h4>
+ hacking.html:<h4>The contrib/ area</h4>
+ hacking.html:<h4>The "obvious fix" rule</h4>
+ hacking.html:<h3>Branch-based development</h3>
+ hacking.html:<h4>Branch creation and management</h4>
+ hacking.html:<h4>Lightweight branches</h4>
+ hacking.html:<h4>BRANCH-README files</h4>
+ hacking.html:<h3>The configuration/build system under unix</h3>
+
+ <h2>Releases</h2>
+ hacking.html:<h3>Release numbering, compatibility, and deprecation</h3>
+ hacking.html:<h4>Reuse of release names</h4>
+ hacking.html:<h4>Deprecation</h4>
+ hacking.html:<h3>Stabilizing and maintaining releases</h3>
+ hacking.html:<h3>Alpha and beta releases</h3>
+ hacking.html:<h3>Signing source distribution packages (a.k.a tarballs)</h3>
+ hacking.html:<h3>Custom releases</h3>
+ release-process.html:<h3>Being the Release Manager</h3>
+ release-process.html:<h3>Creating and maintaining release branches</h3>
+ release-process.html:<h3>Porting changes to release branches</h3>
+ release-process.html:<h3>Managing the <tt>CHANGES file</tt></h3>
+ release-process.html:<h4>Writing the initial content for a branch</h4>
+ release-process.html:<h4>Adding content for patch release</h4>
+ release-process.html:<h3>Preparing to roll a release</h3>
+ release-process.html:<h3>Rolling a release</h3>
+ release-process.html:<h3>Blessing a release</h3>
+ release-process.html:<h3>The actual releasing</h3>
+ release-process.html:<h3>After a release has been made</h3>
+ <h3>How *not* to make a release</h3> (pointer to Hyrum's work)
+
+ <h2>Localization (l10n)</h2>
+ translating.html:<h3>Introduction</h3>
+ translating.html:<h3>Software version requirements</h3>
+ translating.html:<h3>Starting a new translation</h3>
+ translating.html:<h4>Unix (GNU gettext)</h4>
+ translating.html:<h4>Unix (non-GNU gettext)</h4>
+ translating.html:<h4>Windows</h4>
+ translating.html:<h3>Verifying your po file</h3>
+ translating.html:<h3>Submitting your po file</h3>
+ translating.html:<h3>Updating existing po files</h3>
+ translating.html:<h3>Maintenance on branches</h3>
+ translating.html:<h3>Requirements for po and mo files</h3>
+ translating.html:<h3>Conventions for the empty string msgid section</h3>
+ translating.html:<h3>Translation teams</h3>
+ translating.html:<h3>Single versus double quotes</h3>
+ translating.html:<h3>Error message conventions</h3>