−

{{meetingtime|time=20|year=2010|month=04|day=19|nextyear=2010|nextmonth=05|nextday=??|prevyear=2010|prevmonth=03|prevday=15}}

{{meetingtime|time=20|year=2010|month=04|day=19|nextyear=2010|nextmonth=05|nextday=17|prevyear=2010|prevmonth=03|prevday=15}}

== Agenda ==

* Next Meeting Date

** '''May 17th'''

* 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

</div>

*** '''iii is the right option; bartvanassche will look into a fix to build.bat which should be easy as it works in trunk and 5.5'''

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.

</div>

*** '''bartvanassche posted a new patch to -coders that should fix everything; coders are encouraged to voice support (or not) for it'''

*** Release Status

** 5.6 -- hardaker

Exception encountered, of type "Error"