My 2c is that thus far, we've been releasing minor versions (1.1, 1.2, etc.) every 3-4 months, and that that's about right. It's generally good practice in open source to release more often than you do in traditional closed source software. That would put a 1.4 release tag around early Dec for a deployment in late Dec or early Jan. I also don't see us releasing another major version (2.0, 3.0, etc.) at all until something big changes in the platform -- if you look at the roadmap in JIRA, the 2.0 release has some really grand things, like a whole new look & feel. Until then, I see us releasing 1.10, 1.11, etc. if we have to.
-T On Fri, Sep 18, 2009 at 5:56 AM, Sandro Martini <[email protected]>wrote: > Hi Greg, > for me it's Ok, but my only trouble is to ensure that this new release > will not be delivered in a short time immediately after the 1.3, > because in this case the general perception could be that the project > is still evolving too fast (and this is true) because it's not enough > mature (and this is not true). > And if we want to spread to more users this could not be the best ... > > As a best practice we could apply for at least a minor release after a > major, as in most projects. > > What do you think ? > > Sandro >
