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 BryanPendleton
Date Tue, 28 Feb 2006 21:55:29 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/DerbyCommitProcess

------------------------------------------------------------------------------
   * 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 
+    * 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.
+  * The committer informs the developer that the patch has been submitted. The developer
should then do some or all of the following, as appropriate for the particular issue and patch:
     * mark the issue as resolved, if the issue is complete
     * indicate the version(s) in which it is resolved
+    * verify that the original problem is now resolved, and close the JIRA.
-    * 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] .

Mime
View raw message