Ideas (#2) - Version numbers (#474) - Message List
First, may I just say a quick thanks for NSClient++. My colleagues and I have been using it for a couple of years now and have been very impressed with it.
Do you plan to move from 0.x to 1.x any time soon?
I have no issues with the version number myself, as I have found NSClient to be very stable over the years. It is just that management in my organisation assume it is unstable simply because the version starts with 0.x. This is despite the fact that we have had it running without any issues for a couple of years.
I can only assume that you are some sort of perfectionist because I haven't been able to fault it in the last year or so that I've been using it. -I'm figuring that perhaps the current version could be 1.x and a separate alpha/beta version should be made available for whatever part you are currently working on.
I just thought I'd mention it as I'd hate for anyone else to avoid it just because it starts with 0.x.
The thought have struck me yes, especially now that I ene hanve documentation and such...
But in short this is the idea:
- 0.4 "boost based version"
- 0.5 stable boost based version
- 0.6 "extended protocol version"
- 0.7 stable "extended protocol version"
- 0.8 new "plugin api"
- 0.9 stable new "plugin api"
- 1.0 <around here>
Thats the plan... unfortunately just when I am done someone points out a bug, and I spend 3 months fixing it and adding "Minor features" hence 0.3.x has been continuing where it should not :)
But we shall see, I hope to be able to finally!!! stop "minor changes" and instead finish up the almost complete 0.4 version. The problem is that 0.4 has a new settings API and it is a lot of work to keep them in synch so everytime I do something it takes a lot of time to reintegrate the branches.
Michael Medinmickem10/19/09 13:51:52 (4 years ago)