Another 2.0 Pre-Beta Soon

I'm sending out another pre-beta of FuzzMeasure shortly. If you're not on the list, but want to be, please let me know soon. A few folks requested to get onto the list of pre-beta recipients, and rather than sending them a copy of the latest pre-beta, I added them to my mailing list for the next release. I hoped to get the beta out tonight, but I found some small issues I would prefer to clean up first — so I'm now aiming for Monday. If you catch me soon enough, I'll include you in the next round. If you don't reply in time, you'll just have to wait until the next release. After making some tough decisions to remove more features, I can get my public beta out on time. I think that I made a good tradeoff of some missing features to guarantee that I can return to a less-sporadic update schedule. The sooner I get a solid 2.0 foundation out the door, the sooner I can start hammering out some spectacular features to take advantage of that foundation. FuzzMeasure has gone without an update for far too long, and the public really wants to start using 2.0 as soon as possible. I haven't got 100% of the features from 1.3 included in 2.0, but I plan to maintain a frequent update schedule that re-introduces all the functionality 1.3 customers got used to as quickly as possible. To make up for this, I changed FuzzMeasure 2.0 to use a different plist file from 1.3, so that customers can continue using 1.3 and 2.0 on the same machine. Thus, if you got hooked on features in 1.3, you can still have access to them while transitioning to the new release. I hope that this period of transition won't take too long, but I must take this route in order to minimize impact on my customers.