Hello Devs,

I'm back after a fun case of H1N1. I should have more time to put into the project now.

Just looking at what I missed. On 870, I haven't had a chance to review it, but I would like to suggest that commits include only one major change.

This makes them much easier to review, and much easier to remove it they ever prove problematic. It also provides a cleaner history.

I'll check out the actual changes later today.

I agree, one change per commit keeps everything clear for everybody.

I understand that for Joshe at that point it was quite hard to separate his changes as it took him a long time before anything could be checked in. But in the future we should try to avoid this.

Also make sure that when you check something in that it is finished or at least doesn't break anything. I already saw a few strange things in ted which I quickly tried to fix. Didn't have much time last weekend so it was a hack but we should have a look at it. Apparently the time zone name is not set by default which gives all kind of exceptions.

Btw, if you want to do a 'real' review you can create one in FishEye: http://fisheye3.atlassian.com/browse/ted
Just click on the orange logo next to the check in and a review is created. This way we can see each others comments and don't do double work

So if you see something I broke don't hesitate to make a review and point out to me that it doesn't work

Btw, good to have you back Ken! I hope the swine flu wasn't too hard on you.

Couldn't agree more Kenny. Also, we should try to test as much as possible. This will help cut down on the "unknown" breakages that we find.

Kenny, thanks again for the initial review on the maven module separation that I did. I hope to get it committed soon so that I can get back to the web UI stuff.