Lightspeed publication strategy

As long as we're using Lightspeed we can see it's very dynamically developed and published with nightly builds. We appreciate it very much :-)

However we never know when a new, stable version will be published. We are a little afraid of publishing our software using the Lightspeed nightly build. In fact the Lightspeed version we're using is dependent on when we recently had issues to you :-)

Please let us know if you have a particular publication plan (i.e. when Lightspeed 4.1, then 4.2 will be published). We would very appreciate it and then we could plan updates of Lightspeed on our side.

I kindly ask to take a look at this question. It is very important for us to use a stable and tested version for releases of our software.

My apologies, I answered this thread about future planning and thought it was the same thread.

We are looking at releasing a point release (4.1) in the next 2 weeks which will be a wrap up of enhancements since the 4.0 release. In terms of a road map, our typical target is to release a major version approximately ever 12 months. Sometimes this slips but we ship when we're happy with the quality, not because the delivery date arrived.

We typically ship one or two point releases between major versions, depending on the need to roll up fixes and enhancements.

I hope that helps.

Thank you very much for the answer.

IMHO publishing wrap ups of enhancements a few times a year (every half a year or three times a year - in a scheduled manner) as an official minor release, would be great! It would combine both agility of your development (what, again, I very appreciate) and stability of final releases.