Just a quick reminder that the code review of the hackySdt_Issue module has been rescheduled to 11:30 on Wednesday. Find them bugs!
Cheers,
austen
On 4/8/06, Austen Ito <[EMAIL PROTECTED]> wrote:
This Monday (April 10, 2006) at 12:00pm in POST 307, we will review HACK-650 (Issue
SDT Evolution). To perform this review:
(a) Install/update the Eclipse Jupiter plugin.
(b) Install/update and enable the Hackystat Jupiter sensor.
(c) Switch to SVN branch 'branches/HACK-650'
The Jupiter Review ID "HACK-650" has been defined in two modules: hackySdt_Issue
and hackySensor_Jira. Please review the files indicated by the Review ID in those
modules.
I am particularly concerned about the following issues:
* Has the evolution been performed correctly? Do you feel the resulting set of required
and optional fields are appropriate?
* Is the Docbook documentation for the Issue SDT clear? (You might want to
invoke 'ant hackyCore_Build.buildDocBook' to generate the formatted version).
After finishing your review, please be sure to SVN commit your changes. Note that you
will need to SVN 'add' your files (and potentially the review/ directory) before doing
the commit.
---------------------------------------
Supplemental links and resources
The Hackystat Code Review Guidelines:
* http://hackydev.ics.hawaii.edu/hackyDevSite/doc/Review.html
The Elements of Hacky Style:
* http://hackydev.ics.hawaii.edu/hackyDevSite/doc/EHS.html
Jupiter Code Review Tool documentation:
* http://csdl.ics.hawaii.edu/Tools/Jupiter/Core/doc/UsersGuide.html
----------------------------------------
Thanks for reviewing the code!
austen
