Release proposal

[Jan-Henrik Haukeland]

Hi guys

We have around 30 persons on the monit general mailing list, after the
beta was announced this week only two persons actually downloaded the
beta, one was Thomas and the other (I guess) Christian. In other words
we do not get very much feedback from the users on the list.

I suggest a "new" or actually the old release strategy, based on the
assumption that we have to do all the work ourself, including testing.

So, when we, that is the project committers, have tested a monit
release candidate for some time without any incident we simply release
the new candidate as a release (not a beta release). Traditionally
there has been few, if any bugs in previous releases of monit and I
feel that the quality of the current code is good if not better.

Also, traditionally we get more feedback and more users when we do a
new release, since a release includes posting to freshmeat.net. To
release often is also the Linux strategy, it drives the user feedback,
development work and general interest for the product.

As usual, in the "unlikely" case there are bugs we can create a new
bugfix release pretty fast.

What I'm argumenting for here is that we release the current code as
monit 3.0 tomorrow (16. September) or the next day. A release proposal
should be voted on and this is my;

+1

-- 
Jan-Henrik Haukeland