Re: [Devmon] negated threshold patch

[Morsiani, M. <mas...@gi...>]

Hi Buchan,

thanks for your prompt reply.
It's more clear now.

I made a mistake in my last email when I wrote

> Devmon 3 beta3 (the one available on Kaya wiki) is stable?

The right one is

> Is Devmon 3 beta 3 usable (frozen) or still in progress?

That is: Are you working on beta 4 or still working on beta 3?

Moreover.
I agree with you to use two two distinct packages (devmon core, =
template).

What do you think about using devmon-devel mailing list to submit/update =
templates?
Thank you.


Regards.

Massimo Morsiani
Information Technology Dept.
------
Gilbarco S.p.a.
via de' Cattani, 220/G
50145 Firenze, Italy
tel:	+39-055-30941
fax:	+39-055-318603
email:	mas...@gi...
web:	http://www.gilbarco.it


-----Original Message-----
From: Buchan Milne [mailto:bg...@st...]=20
Sent: marted=EC 18 dicembre 2007 13.23
To: dev...@li...
Cc: Morsiani, Massimo
Subject: Re: [Devmon] negated threshold patch

On Tuesday 18 December 2007 12:21:54 Morsiani, Massimo wrote:
> Hi all,
>
> instead of a day-by-day patching, is it possible to have a stable =
release?

Yes, after an upcoming beta.

> Or even a devmon roadmap?

Later (IMHO, we should get another beta out first, before a roadmap).

However, for the actual 0.3.3 release, I would like to see at least:
-working graphs for as much as is possible without significant work -fix =
known bugs related to template features -ship a few more templates for =
common hardware (that exhibits the graphs) -try and understand and/or =
resolve the "devmon tests go purple" issue.

> I'm a little bit confused because is not clear which is devmon=20
> evolution now. Devmon 3 beta3 (the one available on Kaya wiki) is =
stable?

Why would a beta be stable?

> Buchan, Francois,
> do you think to release a single package (devmon core + templates) on=20
> a regular basis? Or do you think to release two distinct packages=20
> (devmon core, template) just like old owner?

I think splitting the software and the templates is fine. However, in =
some cases this is may not lead to a working solution (as the =
patches/templates in this thread show).

In fact, one feature I would like to add is for a template I would like =
to get working ...

> And finally do you want to release
> everything using SVN only?

Of course not, but it's better to have a single source repository =
accessible to everyone, with history (revision control), than for each =
user to have separate source trees and mail patches around (well, at =
least without using an RCS that supports this).


Regards,
Buchan


This message (including any attachments) contains confidential 
and/or proprietary information intended only for the addressee.  
Any unauthorized disclosure, copying, distribution or reliance on 
the contents of this information is strictly prohibited and may 
constitute a violation of law.  If you are not the intended 
recipient, please notify the sender immediately by responding to 
this e-mail, and delete the message from your system.  If you 
have any questions about this e-mail please notify the sender 
immediately.