5.4 Open Issues

I thought it might be worth trying to deal with (or at least come to
some consensus on) the various open issues for 5.4 - so we can
surprise Wes with a clean slate when he gets back from holiday. Well,
a man can dream, can't he?

I've already re-categorised a couple of entries as not really relevant
for 5.4, but we still have the following issues awaiting resolution.
I offer the following list - complete with comments and strawman
proposals - for the purpose of stimulating debate:

1) OpenBSD4 headers
What would be the implications of adding
#include <openbsd3.h>
to openbsd4.h?

2) if-mib rewrite
I believe Robert has already said that he plans a suitable mechanism
to enable this simply. Failing that, we could document setting the CC
env var, but that does feel like a hack.

3) hrStorageIndexes
I'm happy with the current state (unsurprisingly!), though
it's probably
sensible to document the change. Any objections?

4) DisMan event crash
I'll look at this as soon as I get a free minute
(And remember to bring my laptop power cable home with me :-()

5) 64bit nlist
This feels a bit too large a change to consider this late in
the release.
But I admit that I haven't checked the impact of the relevant bugs.
Does anyone want to volunteer to tackle this, or shall we
postpone till 5.4.1?

6) SIGHUP errors
This strikes me as "nice, but not vital".
If I get the time, I'll try to have a look at some of these,
but it doesn't feel worth delaying 5.4 for.

7) perl compiler warnings
If they're simply warnings (rather than errors), then leave till 5.4.1
Unless they actually indicate a more serious problem?

8) "as-needed" linking
Again, I haven't checked the relevant bugs, but this feels as
if it might
be a more significant issue than many of the others.
How damaging would it be to ship things as they currently stand?

9) OS X embedded perl
If it's just embedded perl that's broken, then leave till 5.4.1

10) configure sed failures
See earlier proposal to drop AC_SUBST( *module_list_h )
as a temporary workaround.

R1) TCP notifications
This seems to be the biggy - at least it's the only entry
categorised red.
Do we agree that it needs to be fixed before release, or should it be
re-graded yellow. If it stays red, who understands the problem/code?


Which of these issues are show-stoppers, and which could (reluctantly)
be left till 5.4.1?
Over to you.....

Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders