forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r351898 - in /forrest/site: guidelines.html guidelines.pdf
Date Sat, 03 Dec 2005 05:59:01 GMT
Author: crossley
Date: Fri Dec  2 21:58:56 2005
New Revision: 351898

URL: http://svn.apache.org/viewcvs?rev=351898&view=rev
Log:
Commence new section "Development procedure".

Modified:
    forrest/site/guidelines.html
    forrest/site/guidelines.pdf

Modified: forrest/site/guidelines.html
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.html?rev=351898&r1=351897&r2=351898&view=diff
==============================================================================
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Fri Dec  2 21:58:56 2005
@@ -237,6 +237,9 @@
 <li>
 <a href="#code">Code management</a>
 </li>
+<li>
+<a href="#develop">Development procedure</a>
+</li>
 </ul>
 </div> 
 
@@ -896,6 +899,60 @@
       This enables prompt patch application and eases the load on the individual
       committer. An interesting side-effect is that it encourages community growth.
     </p>
+</div>
+
+  
+<a name="N1030B"></a><a name="develop"></a>
+<h2 class="underlined_10">Development procedure</h2>
+<div class="section">
+<div class="note">
+<div class="label">Note</div>
+<div class="content">
+  This section is still under development. The issues have been discussed
+  on the mailing list. Decisions need to be put into words, so that we do
+  not need to revisit the topic.
+</div>
+</div>
+<p>
+     Development work is done on the trunk of SVN.
+     Wherever possible, functionality is contained in "plugins". 
+     There are "release branches" of SVN, e.g. forrest_07_branch.
+    </p>
+<div class="fixme">
+<div class="label">Fixme (open)</div>
+<div class="content">
+The following issues still need to be added above.
+There are also some relevant email threads, from which we need to extract info.
+</div>
+</div>
+<pre class="code">
+* Define our policy for adding changes to release branch.
+* Define the purpose of the "whiteboard/incubator".
+* Declare that we only really maintain the current release branch
+  (although contributed patches will be applied).
+* When to create a temporary branch for development and when/how to merge.
+  
+
+Some of the many relevant threads in no particular order ...
+
+http://marc.theaimsgroup.com/?t=113344003500003
+Whiteboard usage - rename it to incubator
+
+http://marc.theaimsgroup.com/?t=112798856400001
+Starting a 1.0 development  (Re: [Proposal] rollback)
+
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111968323717620
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111983663526246
+http://marc.theaimsgroup.com/?t=111970529900001
+Project participation and hackability    (was: [VOTE] merge locationmap
+
+http://marc.theaimsgroup.com/?t=112507381300001
+use of whiteboard in forrest
+
+http://marc.theaimsgroup.com/?t=112504310100005
+[Proposal] Development process and a stable trunk
+
+    </pre>
 </div>
 
 <!-- FIXME:

Modified: forrest/site/guidelines.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.pdf?rev=351898&r1=351897&r2=351898&view=diff
==============================================================================
Binary files - no diff available.



Mime
View raw message