The next step in the SDT evolution process is to setup a Jupiter review of the changes you made to your branch. Here's some tips on how to do it:

(1) Make sure your branch (let's call it HACK-631) passes all tests.

(2) Update your Eclipse with the latest version of the Jupiter plugin. The Jupiter home page is: http://csdl.ics.hawaii.edu/Tools/Jupiter

(3) You might want to refresh your memory about how to define Jupiter-based code reviews by consulting the user guide at <http://csdl.ics.hawaii.edu/Tools/Jupiter/Core/doc/UsersGuide.html>.

(3) Define Jupiter reviews for each module affected 'significantly' by your evolutionary activities. Here are some hints:

* For each module (each of which corresponds to an Eclipse project), you are going to have to define a separate Jupiter review. In my case, the two modules affected significantly by my evolution were hackySdt_ReviewActivity and hackySensor_Jupiter. (The hackyApp_Review module was affected, but insignificantly, so I'm not including that in the review. Use your own judgement as to what constitutes "significant" changes).

* Before defining the review ID, you probably want to edit the "default" review ID to specify the reviewer IDs. Define at least the following reviewer IDs: johnson, austen, hongbing, qzhang, mpauldin, jsakuda. As you can see, use people's usernames to simplify things. You probably also want to edit the "author" field for this review to list your user name. The other fields can probably keep their defaults.

* Use the Jira ID as the Review ID. So, in my case, the Review ID is HACK-631. Jupiter requires a separate review for each Eclipse project, but you can use the same Review ID in multiple Eclipse projects. Thus, in my case, I defined the HACK-631 review ID in both the hackySdt_ReviewActivity module and the hackySensor_Jupiter module.

* Check to see if you have to SVN 'add' the resulting .jupiter file.

* Commit your changes to your branch.

(4) Send out an email to the group indicating the availability of the code for review. I will send out my announcement soon as an example.

Cheers,
Philip

Reply via email to