monit-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Status 4.0


From: Martin Pala
Subject: Re: Status 4.0
Date: Tue, 26 Aug 2003 16:16:12 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030711

Jan-Henrik Haukeland wrote:

Seems like the gnu mail server was hit hard by the latest virus and
worm attacks. I could not send this mail on friday but I'll try again
today.

With the latest status from Rory on the porting front, where he got
monit to run on FreeBSD, OpenBSD, and MacOS X (w/o ssl) I think it is
realistic to aim for a release this week. What do others think?

The following is an overview of the todo list before a release AFAIK.

0) Wrap up any remaining port issues
  ---------------------------------
  If Rory finds serious problems after more testing, it may be a
  showstopper, otherwise it's not.

  Responsible: rory


1) Fix line-number problems in the lexer
  -------------------------------------
  The sub-condition for the depend statement in the lexer must be
  rewritten so it count line numbers correctly.

  Responsible: hauk (or maybe Christian?)


2) Finalize documentation.
  ------------------------------------------
  Walk through (QA) the documentation files; monitrc, CHANGES.txt,
  monit.pod, UPGRADE.txt and README and prepare for the release.

  Responsible: hauk + all


3) Prepare and release
  -------------------
  QA everything, tag the release and notify the monit-general list,
  freshmeat.net and address@hidden RPM and Solaris PKG should be
  created after the release and uploaded to savannah.gnu.org.

  Responsible: hauk, QA, CVS tagging, monit.tar.gz and notification
  Responsible: Christian, Solaris PKG ?
  Responsible: Rory, RPM and upload to savannah?
Proposal:

- A new release should not include automatic html doc. generated with
  doxygen. The html doc. adds lots of weight to the tar.gz file and I
  suspect hardly anyone reads it.

+1


FYI:

I have worked with a presentation for monit this week, the purpose is
twofold, 1) Provide and overview and introduction to monit 2) provide
the presentation as a web-introduction for monit.

I have exported the presentation as a set of slides for the web which
can be linked from the monit homepage. To see a preview point your
browser to:

      http://www.tildeslash.com/monit/presentation/index.html

The presentation is a draft and it's not finished and I VERY MUCH WANT
FEEDBACK FROM YOU ON IT. Please use open office to read the
presentation in CVS: monit/doc/presentation.sxi.

I looked on the presentation, i think it is very good. Maybe we can show more monit's power, but we should keep it as simple as possible.

I'm back from vacation - i started to implement monitor/unmonitor actions which can be handed over through dependency. This will solve the problem of security modules such as checksum, permission, uid and gid as discussed on the list. I hope i will have it ready soon and it will be possible to ship it with 4.0 (if developers will agree).

I think we should release 4.0 only after extensive tests - i have problem with time this week, but i will try to do as much as possible.


Martin









reply via email to

[Prev in Thread] Current Thread [Next in Thread]