After some thought, I have decided to declare a one week delay on this review. The basic reason is because we are doing reviews of four page thesis proposals on Thursday, and I am worried that people will not have enough time to review both the code and the proposals adequately. I think the code can be put off for a week more easily than the thesis proposals.

So, Burt, you will have to stumble along for one more week without the wisdom and guidance of the Hackystat Posse. :-)

This also implies that the meeting tomorrow is cancelled.

See you all on Thursday!

Cheers,
Philip

--On Tuesday, September 28, 2004 12:10 PM -1000 Aaron Kagawa <[EMAIL PROTECTED]> wrote:

Greetings, folks:

This Wednesday (09.29.2004) at noon in POST 307, we will be reviewing the Issue Sensor
Data Type (org.hackystat.stdext.issue.sdt) package . To perform this review:

0. Install and/or update (a) the Eclipse Jupiter plug-in and (b) The Hackystat Jupiter
sensor.
1. Checkout/Update the hackyJira module from CVS.
2. Select "IssueSdt" as the ReviewID.

Please review any of the files within that package.

We are particularly concerned about the correctness of the code for a couple of 
reasons.
- It is extremely fresh code and is already on the public server.
- I believe this is Burt's first time implementing a Sensor Data Type.

-------------------------------------------------------------
Supplemental Links and Resources:

The Issue SDT package has the following quality attributes.
* Burt is the primary developer
* Zero unit tests, 26% coverage
* Has never been reviewed

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

Hackystat Jupiter Sensor documentation:
*<http://hackystat.ics.hawaii.edu/hackystat/controller?Page=help&Subpage=install&Sensor
=Eclipse-Jupiter>

Thanks for reviewing the code!

Aaron








Reply via email to