I'd like to recalibrate the version number after 0.1.4 so that we can make proper use of all the version positions (major.minor.patch). As it stands now, we are using the patch number as the minor number. We want to set expectations right and give ourselves room to do patch releases--the latter being the biggest problem right now.
I think we've already done our 1.0.0 release as 0.1.0. Putting out a 1.0.0 release now would appear as though we are replaying past events. Therefore, I propose the following jump:
0.1.4 => 1.5.0
The reason I like this change is because it's very clear that what we are doing is recalibrating and not necessarily making a major change to the software. Then we can set course for 2.0.0 as our next big destination, with 1.6.0, 1.7.0, ... and any patch releases along the way.
Sound good?
-Dan
p.s. I'm planning to send out a 0.1.4 release outlook in a few days. Sorry I missed sending one for 0.1.3. Though, you can always look at the milestones in the issue tracker to get an idea of what is planned for the release.
--
Locked
