Re: Struggling with net-snmp agent SNMPv1 traps

> Unfortunately, the follow-up procedure is based on available developer time.
> And like most developers, we generally tend to focus more on new code, rather
> than bug fixing.  But this is a significant bug, so I bumped the priority in
> the bug db.

Well, I have to admit that I don't tend to take a great deal of notice
of the priority settings.   When I'm blitzing the bug list, I tend to
start at a given point, and work through them in order.
   If I feel that I can tackle a particular bug, then I'll do so.
If I don't feel competent to address it, I'll skip it and move on to
the next one.   The colour of the bug is irrelevant to this process.


>          It should get fixed before 5.1.1 goes out (whenever that is).

It feels as if we ought to be thinking about getting this out
fairly soon.   It's certainly been long enough since 5.1.

How about the following provisional timescale:

        2 weeks blitz on outstanding bugs

        Feb 6   net-snmp-5.1.1.pre1
        Feb 13  net-snmp.5.1.1.rc1
        Feb 20  net-snmp.5.1.1

??

That allows for a week's-worth of slippage, and we could still ship
before the end of February.

I'm coming to a natural pause in my documentation efforts, and
it would make a pleasant change to be coding again....

Dave



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@xxxxxxxxxxxxxxxxxxxxx
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users