Re: [Devmon-devel] [Devmon] new beta devmon-0.3.0-beta4

[xbgmsharp <xbg...@gm...>]

Hello,

I have subscribe to devmon-devel.
We can use a bug tracker.

I have also resolved most of the issues I had, which is why the beta4 =20
is allready in production, in fact i agree with you. Better if it is a =20
released version.

Have you read my documentation about graphing?
While modify Hobbit for BBwin, i have redo my if_ patch a lot more nicer.
Maybe we should include it in the documentation?
Maybe we should complete the documentation?
I didn't undestand what exactly you want to graph?

I am also starting to add a serial colunm in order to collect serial =20
number for all cisco devices. Almost done, i will commit it probably =20
by the end of the week.

Redgards,
Francois Lacroix.



Buchan Milne <bg...@st...> a =E9crit :

> On Monday 31 December 2007 14:38:47 Buchan Milne wrote:
>> On Thursday 27 December 2007 14:45:10 xbgmsharp wrote:
>> > Hello,
>> >
>> > What is new since devmon-0.3.0-beta3 :
>> >
>> > - Now one OID equal one SNMP request intead of all oids leaf in one
>> > request. - Add negate the threshold regexp
>> > - Fix hostname fqdn
>> > - Add Cisco-ASA template
>> > - Fix F5-bigip-lite template
>> > - Add documentation and script for GRAPHING
>> >
>> > All of this is avalaible for testing via the SVN.
>> > http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/
>> > http://sourceforge.net/svn/?group_id=3D160720
>> > http://devmon.sourceforge.net/
>> >
>> > Please Feedback and reports any problem or error.
>> >
>> > To get error msg use this option '--debug -f -vvvvvv'.
>>
>> I think we should actually create releases on sourceforge, just to make i=
t
>> easier for users to test.
>>
>> In fact, this is what should happen when releasing:
>>
>> -make final changes
>> -commit
>> -change version number
>> -commit
>> -tag (with svn co to /tags/release-0_3_0_beta4, I'll give a full example
>> next time I do this)
>> -create a clean tarball release (I may add a make file with basic targets
>> to automate this)
>> -make the tarball available from the sourceforge file release system.
>>
>> Let's try it for the next release, whether it is a beta or final of 0.3.0=
.
>> However, I will tag this release in svn soon, hopefully before any change=
s
>> are made.
>
> I tagged the release in svn before any of the changes I made.
>
>> (please use devmon-devel for issues pertaining solely to development ... =
I
>> have also activated the svn commit hook to this list)
>
> The svn hook wasn't  activated properly, I activated it again over the
> weekend, and my last commit did go to the mailing list (after moderator
> approval, and whitelisting of my sourceforge address on the mailing list).
>
> Francois, please subscribe, and let me know when you have, as I think we
> should start coordinating for release.
>
> Also, I was going to ask people who have tested beta4 (or, who test the ne=
xt
> pre-release tarball) to list any issues they are aware of. However, I thin=
k
> it would be best to use a bug tracker for this. So, should we start using =
the
> SourceForge tracker for issues ?
>
> I have resolved most of the issues I had, and am almost ready to  =20
> move 0.3.0 to
> our production system ... but I would prefer it to be a released version i=
f
> possible ....
>
> Besides one or two minor issues I will discuss on the devmon-support =20
>  list, the
> last thing I think we should consider delaying release for could be a devm=
on
> rrd collector (patch) for Hobbit (I didn't get time over the weekend for t=
his
> though).
>
> Regards,
> Buchan
>
>

--=20
Thanks for using xbgm# / Devmon / BBwin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
http://bbwin.sourceforge.net/
Please feedback.