Yeah, the problem is never really build any "stable" versions between the major releases. *g* That is, I try to keep them stable all the time. But I don't want to have an additional commit with the version change after each 2nd or 3rd normal commit 😉.
I think with the existing "source tree" usage of Sparrow, that wasn't much a problem (the "version" could be seen by running 'git log' on the Sparrow repository); but with the ".framework" deployment, that's no longer possible. Although: I actually don't plan to release those inbetween the official, stable releases, anyway.
I think the best solution would really be to develop Sparrow in smaller steps, i.e. release stable versions more often.