>>>>> On Sun, 2 Oct 2005 09:55:46 +0100, Dave Shield <[EMAIL PROTECTED]> said:
Dave> But surely what we're interested in providing (by default) is the
Dave> Event-MIB *functionality*, rather than a particular implementation?
I think Robert's point should be if we're turning it on by default it
should be somewhat well tested code. However, this is also a case
where the code does nothing until configured so I doubt it's a big
deal as far as a default config of not-on goes. The only question
left becomes: how sure are we that it works at least as good as or
better than the current version such that all the people that are
using the current version in production environments will feel secure
that we've done this without a huge amount of testing? That's the
only question that worries me much...
>> Might I suggest a configure flag (--enable-disman-rewrite) for 5.3,
>> with the switch to the new version as the default in 5.4?
Dave> What's the point of that?
I think the point would be to give developers one more release cycle
to test it.
I think we should have some more flags configured on by default for
cvs checkouts... This would be an example of one, as well as the mfd
rewrites should default to on for cvs. IE, if you're checking out CVS
you get the newest code by default.
I think on the whole, I'm inclined to agree with Dave and say it could
go into 5.3 as long as:
1) he finishes it
2) he really really does believe it'll be less prone to bugs/errors
than the current code.
But I'm only barely on that side of the fence.
--
Wes Hardaker
Sparta, Inc.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
