Difference between revisions of "Notes20100419"
From Net-SNMP Wiki
Line 5: | Line 5: | ||
* Next Meeting Date | * Next Meeting Date | ||
+ | ** | ||
* Releases | * Releases | ||
** 5.2.x -- dts12 | ** 5.2.x -- dts12 | ||
** 5.4.x -- dts12 | ** 5.4.x -- dts12 | ||
+ | ** Text sent from dts12: | ||
+ | With one exception, I believe the 5.4.3 and 5.2.6 | ||
+ | releases are ready to go out. That exception is, | ||
+ | of course, the status of the Windows builds. | ||
+ | |||
+ | There are two issues here: | ||
+ | a) Notification Log MIB | ||
+ | b) IPv6 support | ||
+ | |||
+ | As it stands at the moment, the code (for both lines) | ||
+ | builds OK using both Visual Studio (run interactively) | ||
+ | and using 'build.bat'. However previous versions of the | ||
+ | 5.4.x agent & trapd included support for the Notification | ||
+ | Log MIB when built with Visual Studio, and this is no | ||
+ | longer active. | ||
+ | |||
+ | I believe there are three options here: | ||
+ | i) Accept the current code | ||
+ | (build.bat works, MSVC build loses functionality) | ||
+ | ii) Reactivate the NLog-MIB support | ||
+ | (MSVC works as before, build.bat fails) | ||
+ | iii) Add support to build.bat framework to include NLog | ||
+ | |||
+ | Let me know what the meeting decides, and we'll take it from | ||
+ | there. If we go with either i) or ii), then I'll update the | ||
+ | documentation to describe how users can fix whichever problem | ||
+ | remains. (It's a trivial, one-line edit) | ||
+ | |||
+ | As regards IPv6 support, the current status is (I believe) | ||
+ | that MSVC builds OK, but (definitely) build.bat fails when | ||
+ | IPv6 support is enabled. The patch I proposed is apparently | ||
+ | not suitable - Bart is looking to come up with a better version. | ||
+ | |||
+ | There are two options here: | ||
+ | I) Accept the current code | ||
+ | (and document that build.bat does not support IPv6) | ||
+ | II) Use whatever fix Bart comes up with. | ||
+ | |||
*** Release Status | *** Release Status | ||
** 5.6 -- hardaker | ** 5.6 -- hardaker |
Revision as of 19:03, 19 April 2010
Net-SNMP Meeting
2010-04-19
2010-04-19
Previous: | 2010-03-15 |
Next: | 2010-05-?? |
This is the meeting agenda/notes for the Meeting held on 2010-04-19.
Date and Time: 2010-04-19 20:00 UTC
Agenda
- Next Meeting Date
- Releases
- 5.2.x -- dts12
- 5.4.x -- dts12
- Text sent from dts12:
With one exception, I believe the 5.4.3 and 5.2.6 releases are ready to go out. That exception is, of course, the status of the Windows builds. There are two issues here: a) Notification Log MIB b) IPv6 support As it stands at the moment, the code (for both lines) builds OK using both Visual Studio (run interactively) and using 'build.bat'. However previous versions of the 5.4.x agent & trapd included support for the Notification Log MIB when built with Visual Studio, and this is no longer active. I believe there are three options here: i) Accept the current code (build.bat works, MSVC build loses functionality) ii) Reactivate the NLog-MIB support (MSVC works as before, build.bat fails) iii) Add support to build.bat framework to include NLog Let me know what the meeting decides, and we'll take it from there. If we go with either i) or ii), then I'll update the documentation to describe how users can fix whichever problem remains. (It's a trivial, one-line edit) As regards IPv6 support, the current status is (I believe) that MSVC builds OK, but (definitely) build.bat fails when IPv6 support is enabled. The patch I proposed is apparently not suitable - Bart is looking to come up with a better version. There are two options here: I) Accept the current code (and document that build.bat does not support IPv6) II) Use whatever fix Bart comes up with.
- Release Status
- 5.6 -- hardaker
- Release Testing
- Binary Releases
- Administrative
- Test server updates
- Technical Discussions
- Round Table -- What are ya up to?