I write tools because I’m lazy – if I can create something to take care of some of the drudgery, I’m happy. That means that when I think of something that could be added to save some steps, I add it. And release a new version.
I have another product that was updated 18 times in the last 12 months.
Some people might think that’s excessive, but if I add something to a program that can help someone (like it helps me), why should I wait for an “official release date?” (Nothing snide meant against Ansca – Corona SDK is on a much larger scale (at this point) than CPM, so they have more hoops to jump through for each release.)
You can see what tweaks have been made, bugs stomped, and features added on the blog: http://coronaprojectmanager.com/blog/
I try and list the changes made in each version and if you don’t want to upgrade each time, no big deal – you can safely skip some and upgrade when you want to.
I just released v1.2.1 to fix a problem a couple people reported and am planning on v1.3 in a couple weeks – but while driving home from the store a couple hours ago I thought of a way to handle something that’s been bugging me (it’s not “broken” it just isn’t as smooth as it could be) so I may add that as v1.3 and release that in a day or so – and then bump the bigger changes to a v1.4 in a couple weeks.
Just in case you wondered what the deal is with so many releases so close together, that’s the scoop. I use the software I write and when I see a deficiency (or have one pointed out to me) I try to fix it and get it out as soon as possible.
Jay
[import]uid: 9440 topic_id: 4387 reply_id: 304387[/import]