One issue one patch (one comment)

Added by Tsuy Ito, last edited by Tsuy Ito on Aug 18, 2009  (view change)

Solution 1

Step 1 - 4 are the same as before done by the developer (dev). The reviewer (rev) has to do step 5 - 10. The additional steps are 7 - 9.

  1. dev: use tx-openissueonproject to clone the default on trialox.org (creates ISSUE-XY on trialox.org)
  2. dev: use tx-cloneissue to have a working copy (creates ISSUE-XY on the dev's computer)
  3. dev: commit and push to the issue on trialox.org
  4. dev: use tx-updatefromdefault
  5. dev: use hg diff (http://mercurial.selenic.com/wiki/RdiffExtension) from default repo with issue repo as first argument and redirect the output to a file (e.g hg diff PATH-TO/ISSUE-XY/ARTEFACT-ID > ISSUE-XY_ARTEFACT-ID.patch)
  6. dev: create a folder called ISSUE-XY in the folder "patches" on trialox.org
  7. dev: resolve issue
  8. rev: download patches from th issue
  9. rev: use tx-cloneissue to clone the default repos of the affected projects
  10. rev: review patches / apply patches (e.g. hg import -m "ISSUE-XY: message" ISSUE-XY.patch) and then review the issue
  11. rev: Push patched default to trialox.org
  12. rev: If reviewer fixed some typos or made some minor changes commit them separately.
  13. rev: remove folder ISSUE-XY from trialox.org

Solution 2

Solution 2 is more complicated to apply to the current development process

More information could be found on the following web pages:

http://mercurial.selenic.com/wiki/MqExtension
http://hgbook.red-bean.com/read/mercurial-queues-reference.html
http://hgbook.red-bean.com/read/managing-change-with-mercurial-queues.html

 A possible workflow could be 

Labels

 
(None)