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 "DerbyCommitProcess" by DanDebrunner
Date Thu, 23 Feb 2006 17:30:17 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 DanDebrunner:
http://wiki.apache.org/db-derby/DerbyCommitProcess

------------------------------------------------------------------------------
  
   * A JIRA entry is filed, describing the necessary change
   * The developer who is working on the problem assigns the entry to herself, and develops
a change:
-    * A change proposal is developed.
+    * A change proposal is developed, see some advice PatchAdvice.
     * The developer attaches the change proposal, in "svn diff" format, to the JIRA entry
     * Other Derby developers review the change proposal and provide feedback.
     The above three steps are repeated until there is consensus that the change is ready.
@@ -15, +15 @@

     * close reading of the diff, 
     * exploratory testing of specific changes of interest, 
     * verifying that the regression test(s) fail without the code change(s) and pass once
the code changes are applied.
-  * When the committer is satisfied that the change is ready, the committer issues the "svn
commit" to commit the change. In the commit log message, the committer should include information
that ties back to the JIRA issue and to the developer who made the change.
+  * When the committer is satisfied that the change is ready, the committer issues the "svn
commit" to commit the change. In the commit log message, the committer should include information
that ties back to the JIRA issue (the Jira bug number in the format DERBY-XXX anywhere in
the commit message) and to the developer who made the change.
   * The committer updates the JIRA entry to:
     * clear the "patch available" checkbox 
-    * mark the issue as resolved
+    * mark the issue as resolved, if the issue is complete
     * indicate the version(s) in which it is resolved
-    * include a comment with information about the revision number, for example as a hyperlink
to the SVN revision viewer for that revision.
+    * include a comment with information about the revision number, for example as a hyperlink
to the SVN revision viewer for that revision. If the Jira issue number was correctly entered
in the svn commit log message, then Jira will automatically pick up the commit message and
link to SVN revision viewer in the Subversion Commits tab.
   * Either the developer or the original assignee should then verify that the patch was successfully
applied, and that the original problem is now resolved, and closes the JIRA.
  
+ 
+ Note that Derby as a Apache DB sub-project follows the [http://db.apache.org/guidelines.html
Apache DB guidelines] .
+ This includes the [http://www.apache.org/foundation/glossary.html#CommitThenReview Commit-Then-Review]
policy.
+ 

Mime
View raw message