db-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r843162 - in /websites/staging/db/trunk/content: ./ sitemap.html source-repos.html source.html
Date Wed, 19 Dec 2012 22:37:35 GMT
Author: buildbot
Date: Wed Dec 19 22:37:35 2012
New Revision: 843162

Staging update by buildbot for db

    websites/staging/db/trunk/content/   (props changed)

Propchange: websites/staging/db/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 19 22:37:35 2012
@@ -1 +1 @@

Modified: websites/staging/db/trunk/content/sitemap.html
--- websites/staging/db/trunk/content/sitemap.html (original)
+++ websites/staging/db/trunk/content/sitemap.html Wed Dec 19 22:37:35 2012
@@ -109,7 +109,7 @@
 <li><a href="/management.html">PMC Bylaws</a></li>
 <li><a href="/newproject.html">Subproject Proposals</a></li>
 <li><a href="/roles.html">Roles and Responsibilities</a></li>
-<li><a href="/source-repos.html">Source Repositories</a></li>
+<li><a href="/source.html">Source Repositories</a></li>
 <li><a href="/whoweare.html">Who We Are</a></li>

Added: websites/staging/db/trunk/content/source.html
--- websites/staging/db/trunk/content/source.html (added)
+++ websites/staging/db/trunk/content/source.html Wed Dec 19 22:37:35 2012
@@ -0,0 +1,237 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+       http://www.apache.org/licenses/LICENSE- 2.0
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+    <link href="css/site.css" rel="stylesheet" type="text/css">
+    <title>Apache DB Project - Source Repositories</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<div class="white_box">
+<div class="header">
+    <div id="header_background">
+        <div id="db_logo">
+            <table>
+                <tbody>
+                    <tr>
+                        <td>
+                            <a href="http://db.apache.org/"><img alt="Apache DB
logo" src="/images/db-logo.png"/></a>
+                        </td>
+                        <td>
+                            <a href="http://db.apache.org/" id="projectLogo">The Apache
DB Project</a>
+                        </td>
+                    </tr>
+                </tbody>
+            </table>
+        </div>
+    </div>
+<div class="content">
+      <div>
+    <table border="0">
+    <tbody>
+        <tr>
+        <td valign="top" width="250px">
+          <div class="navigation">
+            <div class="navigation_top">
+              <div class="navigation_bottom">
+<!-- sidenav -->
+<h3 id="apache-db">Apache DB</h3>
+<li><a href="index.html">About / News</a></li>
+<li><a href="http://www.apache.org/licenses/">License</a></li>
+<li><a href="mail.html">Maling Lists</a></li>
+<li><a href="whoweare.html">Who We Are</a></li>
+<li><a href="source-repos.html">Source Repositories</a></li>
+<h3 id="subprojects">Subprojects</h3>
+<li><a href="http://db.apache.org/ddlutils/">DdlUtils</a></li>
+<li><a href="http://db.apache.org/derby/">Derby</a></li>
+<li><a href="http://db.apache.org/jdo/">Java Data Objects (JDO)</a></li>
+<li><a href="http://db.apache.org/torque/">Torque</a></li>
+<h3 id="retired-subprojects">Retired Subprojects</h3>
+<li><a href="http://attic.apache.org/projects/ojb.html">ObJectRelationalBridge</a></li>
+<h3 id="the-foundation">The Foundation</h3>
+<li><a href="http://www.apache.org">Apache</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
+<h3 id="search">Search</h3>
+<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size:
+ <input type="hidden" name="sitesearch" value="db.apache.org">
+ <input type="text" id="query" name="q" size="20" maxlength="255" >
+ <input type="submit" value="Search Apache DB" id="submit"/>
+<!-- sidenav -->
+              </div>
+            </div>
+          </div>
+        </td>
+        <td style="overflow: hidden;" valign="top">
+          <div class="wiki-content">
+<h1 id="source-repositories">Source Repositories</h1>
+<p>The Project's codebase is maintained in shared information repositories using
+Subversion. Only Committers have write access to these repositories. Everyone
+has anonymous read access.</p>
+<p>All Java Language source code in the repository must be written in
+conformance to the 
+<a href="http://www.oracle.com/technetwork/java/codeconvtoc-136057.html">Code Conventions
for the Java Programming Language</a> as published
+by Sun, or in conformance with another well-defined convention specified by
+the subproject.</p>
+<h2 id="license">License</h2>
+<p>All source code committed to the Project's repositories must be covered by
+the <a href="http://www.apache.org/foundation/licence-FAQ.html">Apache License</a>
+contain a copyright and license that allows redistribution under the same
+conditions as the Apache License.</p>
+<p>Committers should update the copyright notice on the Apache License to
+include the current year when they revise a source file. If it is 2002, and
+you revise a source file from 1999, change the copyright notice in the
+license to cite "1999, 2002". If the file was from 2001, we would change it
+to 2001-2002. And so forth. This will happen most often in the early part of
+a year, but maintenance of the copyright date should occur year-round, as
+<p>Any code, document, or binary that is committed to the Project's
+repositories, but not being donated to the ASF, must be clearly marked as
+such. All contributors should have a
+<a href="http://www.apache.org/licenses/#clas">Contributor License Agreement</a>
+<p>Any JAR committed to the Project's repositories <strong>must</strong>
be licensed for
+redistribution. BSD and MPL style licenses are generally fine, but many Sun
+JARs do not permit redistribution.</p>
+<h2 id="status-files">Status Files</h2>
+<p>Each of the Project's active source code repositories contain a file named
+STATUS which is used to keep track of the agenda and plans for work within
+that repository. The status file includes information about release plans, a
+summary of code changes committed since the last release, a list of proposed
+changes that are under discussion, brief notes about items that individual
+developers are working on or want discussion about, and anything else that
+may be useful to help the group track progress.</p>
+<p>It is recommended that the active status files are automatically posted to
+the developer mailing lists three times per week.</p>
+<h2 id="branches">Branches</h2>
+<p>Groups are allowed to create a branch for release cycles, etc. They are
+expected to merge completely back with the main branch as soon as their
+release cycle is complete. All branches currently in use should be documented
+by the respective projects. For example,
+<a href="http://db.apache.org/derby/dev/derby_source.html#Branches">Derby</a>
has a page
+on the site that details the branches currently in use.</p>
+<h2 id="changes">Changes</h2>
+<p>Simple patches to fix bugs can be committed then reviewed. With a
+commit-then-review process, the Committer is trusted to have a high degree of
+confidence in the change.</p>
+<p>Doubtful changes, new features, and large scale overhauls need to be
+discussed before committing them into the repository. Any change that affects
+the semantics of an existing API function, the size of the program,
+configuration data formats, or other major areas must receive consensus
+approval before being committed.</p>
+<p>Related changes should be committed as a group, or very closely together.
+Half complete projects should never be committed to the main branch of a
+development repository. All code changes must be successfully compiled on the
+developer's platform before being committed. Also, any unit tests should also
+<p>The current source code tree for a subproject should be capable of complete
+compilation at all times. However, it is sometimes impossible for a developer
+on one platform to avoid breaking some other platform when a change is
+committed. If it is anticipated that a given change will break the build on
+some other platform, the committer must indicate that in the commit message.</p>
+<p>A committed change must be reversed if it is vetoed by one of the voting
+members and the veto conditions cannot be immediately satisfied by the
+equivalent of a "bug fix" commit. The veto must be rescinded before the
+change can be included in any public release.
+<p>When a specific change to a product is proposed for discussion or voting on
+the appropriate development mailing list, it should be presented in the form
+of input to the patch command. When sent to the mailing list, the message
+should contain a Subject beginning with [PATCH] and a distinctive one-line
+summary in the subject corresponding to the action item for that patch.</p>
+<p>The patch should be created by using the svn diff command from the original
+software file(s) to the modified software file(s). It is recommended that you
+submit patches against the latest Subversion versions of the software in
+order to avoid conflicts. This will also ensure that you are not submitting a
+patch for a problem that has already been resolved.</p>
+<p>For example:</p>
+<div class="codehilite"><pre>    <span class="n">diff</span> <span
class="o">-</span><span class="n">u</span> <span class="n">Main</span><span
class="o">.</span><span class="n">java</span><span class="o">.</span><span
class="n">orig</span> <span class="n">Main</span><span class="o">.</span><span
class="n">java</span> <span class="o">&gt;&gt;</span> <span
class="n">patchfile</span><span class="o">.</span><span class="n">txt</span>
+<p>or (preferred)</p>
+<div class="codehilite"><pre>    <span class="n">svn</span> <span
class="n">diff</span> <span class="n">Main</span><span class="o">.</span><span
class="n">java</span> <span class="o">&gt;&gt;</span> <span
class="n">patchfile</span><span class="o">.</span><span class="n">txt</span>
+<p>or (Win32)</p>
+<p>You can use a GUI front-end for <a href="http://subversion.apache.org/">Subversion</a>,
+or you can install <a href="http://www.cygwin.com">Cygwin</a> which will enable
you to
+use the bash shell and also installs a lot of other utilities (such as diff
+and patch) that will turn your PC into a virtual Unix machine.</p>
+<p>All patches necessary to address an action item should be concatencated
+within a single patch message. If later modification to the patch proves
+necessary, the entire new patch should be posted and not just the difference
+between the two patches.</p>
+<p>If your email client line wraps the patch, consider placing the patch file up
+on a website and sending a message to the development list with the URL so
+that the developers with commit access can download the commit the patch file
+more easily. You can also add the patch as part of a bug report.</p>
+<p>When a patch has been checked into Subversion, the person who checked in the
+patch should send a message to the person who sent the patch in as well as
+the mailing list specifying that the patch has been checked in. The reason is
+that not everyone watches commit messages and it is helpful for others to
+know what has been checked in and when in order to help prevent people from
+applying the patch at the same time.</p>
+          </div>
+        </td>
+        </tr>
+    </tbody>
+        </table>
+  </div>
+<div class="black_box">
+<div class="footer">
+  <div class="footer_l">
+    <div class="footer_r">
+      <div>
+      </div>
+    </div>
+  </div>
+<div id="copyright_footer">
+<p>Copyright &copy; 2012 The Apache Software Foundation, Licensed under the <a
href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br>Apache
and the Apache feather logo are trademarks of The Apache Software Foundation.</p>

View raw message