Much Work To Do... Before Making Absolutely No Progress

Aight... so here's how my ConsultComm development schedule goes:

1. Get coffee
   
2. Make change to fix some bug due to a tweak I made in NetBeans 5.0
   
3. Find way to fix things so RPM builds work correctly
   
4. Spend 30 minutes trying to work around SourceForge problems that have existed since the dawn of ages
   
5. Spend another 30 minutes uploading files and publishing new beta revision
   
6. Mark bugs as closed, send e-mails
   
7. Rinse, repeat
   

So... for point releases only 20-40% of my time is spent actually writing code. Kinda drives you batty after a while.

But, if anyone is inclined, take the latest beta release for a test drive.