Here's how it goes:
- You plan for what needs to be fixed in a patch
- You begin to code the patch and unit test each fix
- You test the program overall to make sure nothing else was broken
- You release the patch
See, in the case of 1.0.2 (39), step 2 was going so well. I made it through all but one of the fixes in a little over a day. How could I not finish that last item, I had all day!
I didn't finish that last item. It's just being stubborn.
So I'll work on getting it out again today, but no promises this time (maybe that'll help keep Murphy off my back). It's a really good patch, so hang on and I'll get it to you ASAP!
The upside is, I have a real download stat still (118,000+ copies). Judy also noticed that I lost my featured product status on Apple's all categories page (Toon Boom Studio snatched it away), but I still have the business and finance page and I'm still near the top of the most downloaded list. That means I have a little more time to work out my marketing plan for after I lose the cherished Apple spot.