Quicky quiz:
Question: What's the absolute worst time to commit a large number of changes to a
system?
Answer: 5:00pm on a Friday
So I guess I'm OK, because I've just committed a bazillion changes to a quinjillion files
but it's only 4:55pm. :-)
The deed is done, evolutionary SDTs are now incorporated into the system. I did a local
freshStart junitAll on what should be the equivalent of hackystat-ALL and everything is
passing fine. We'll see whether hackydev decides to mock my attempts at quality
assurance tonight.
A few things to note:
1. Every module with an SDT has been modified. Please do a cvs update to get
the changes.
2. While the unit tests (such as they are) for sensors (i.e hackyEmacs, etc.) pass, this
is only because the tests aren't robust enough to detect the fact that the sensors are
broken. Trust me, none of the sensors will work given the new underlying code base.
3. Fortunately, fixing the sensors is quite easy and should only take a few minutes per
sensor. To understand what's changed, I've rewritten the evolutionary SDT document from
scratch. It used to be a proposal for a redesign, now it is a tutorial/developer guide
on the new version of SDTs. It's available at:
- <http://hackydev.ics.hawaii.edu/hackyDevSite/doc/evolutionarySDT.html>
4. I would like to distribute sensor upgrade duties at the CSDL meeting on Monday, as
well as have a general discussion of evolutionary sensor data types. So, I would like to
request that all CSDL folks read the above document and email me comments on it prior to
the Monday meeting. Of course, comments from everyone are solicited and welcomed. If I
have time, I'll upgrade a sensor or two over the weekend to provide an illustration of
what needs to be done.
Have a good weekend.
Cheers,
Philip
