db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyCommitHowTo" by BryanPendleton
Date Sat, 04 Mar 2006 00:32:59 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by BryanPendleton:
http://wiki.apache.org/db-derby/DerbyCommitHowTo

------------------------------------------------------------------------------
  = Committing patches to the Derby Subversion Repository =
  
- Oyvind Bakksjo compiled this set of notes to guide Derby committers through the low-level
mechanics of committing a change to Derby. These notes are best read within the larger context
of the DerbyCommitProcess.
+ Based on a previous document by Oyvind Bakksjo, here are a set of notes to guide Derby committers
through the low-level mechanics of committing a change to Derby. These notes are best read
within the larger context of the DerbyCommitProcess.
  
  Committing contributions from others is not as straightforward as one might think. This
mainly stems from the fact that there is an {{{svn diff}}} command, but there is no {{{svn
patch}}} command. There are a number of things to remember; if not done carefully, you might
end up doing partial commits that may break the build. This page attempts to give a recipe
for safely committing code contributions. 
  
@@ -31, +31 @@

     * possibly running some or all of the [http://svn.apache.org/repos/asf/db/derby/code/trunk/java/testing/README.htm
regression test suites], as the committer deems relevant. Check that tests pass. If they do
not:
       * Check the nightly/tinderbox for the same failure.
       * Verify that the failure is not caused by the patch.
-  * Commit the patch with {{{svn commit}}}. Use either {{{--message}}}, {{{--file}}} or {{{--editor-cmd}}}.
Include the following in the commit message:
+  * Commit the patch with {{{svn commit}}}. Use either {{{--message}}}, {{{--file}}} or {{{--editor-cmd}}}.
Include the following in the commit log message:
     * The ID of the JIRA issue. Make sure you use the format DERBY-NNN so that JIRA picks
it up.
     * Some text explaining what the patch does (typically snipped from the JIRA issue).
     * The contributor's name/email.
-  * Send out an email to let people know you have committed the patch. This is done automatically
if you post the information as a comment to the JIRA issue.
+  * Notify the contributor and the community that the patch has been committed, according
to the DerbyCommitProcess.
  

Mime
View raw message