+1 to move to 1.0. We have done the same thing with Apache Aries moving Blueprint from 0.5 to 1.0 release
On Mon, Nov 11, 2013 at 6:17 PM, John D. Ament <john.d.am...@gmail.com>wrote: > Yep, agreed. Users care about the version #. I would recommend that if we > could release a 1.0 based on the current code base + some additional bug > fixes we'll get huge wins. > > +1 to switching current to 1.0.0-SNAPSHOT. > > > On Mon, Nov 11, 2013 at 12:08 PM, Mark Struberg <strub...@yahoo.de> wrote: > > > Hi! > > > > In the last 2 months I did a few conference talks and smaller > > presentations (OpenBlend, W-JAX, ..) and always got the same questions: > > "it's only a 0.x version, so is it already stable? I don't like to use it > > in production with 0.x" > > > > And the actual answer is: "well, core, cdictrl, etc are stable since a > > long time, other modules are not yet 100% where we like them". > > > > The other fact is that we will never get all our modules 100% stable. > > Because new modules cannot be released with the same quality than > > established and well known and bugfixed modules. > > > > Thus I think we should rather introduce a kind of majurity-matrix for > > DeltaSpike. > > A simple list of modules and their majurity grade. > > > > > > > > By officially moving to 1.0 we would gain much more users. > > I personally do not care about numbers, but LOTS of users do! > > > > Wdyt? > > > > LieGrue, > > strub > > > -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
