Difference between revisions of "Notes20100222"

From Net-SNMP Wiki
Jump to: navigation, search
Line 22: Line 22:
 
* Coding Issues
 
* Coding Issues
 
** RPM API incompatibilities
 
** RPM API incompatibilities
 +
*** 5.[2-4] has issues with RPM
 +
*** jsafrane suggests you probably need -D_RPM_4_4_COMPAT
 +
*** '''jasfrane''' will look into the problem
 
** Noting the new [[Command Line Calling Order]] page -- Wes
 
** Noting the new [[Command Line Calling Order]] page -- Wes
 
** Transport changes likely coming soon
 
** Transport changes likely coming soon

Revision as of 20:23, 22 February 2010

Previous: 2010-01-11
Next: 2010-03-15

This is the meeting agenda/notes for the Meeting held on 2010-02-22.

Date and Time: 2010-02-22 20:00 UTC

Agenda

  • Next Meeting Date
    • Mar 15th
  • Releases
    • 5.2.x -- dts12
      • Dave is deleday due to work. Will likely do one more pre-release
    • 5.4.x -- dts12
      • Dave is delayed due to work. Will likely do one more pre-release
    • 5.6 in May/June?
      • Wes proposes this
      • difficult but ok to shoot for -- Wes
      • discussion surrounding "what's in it"
        • isms support among other things
      • No real objections, but no real support either
      • result: probably; confirm next time
  • Administrative Issues
    • Wes reminds that we backport patches to all branches possible, but only fixes (no features).
  • Coding Issues
    • RPM API incompatibilities
      • 5.[2-4] has issues with RPM
      • jsafrane suggests you probably need -D_RPM_4_4_COMPAT
      • jasfrane will look into the problem
    • Noting the new Command Line Calling Order page -- Wes
    • Transport changes likely coming soon
      • Resulting from TLS work mainly
      • Changes involved:
        • auto-transport detection and inclusion
          • similar to mib modules now
          • signficinantly more re-use
        • Configuration passing
        • possible split of transport object creation to actual opening
    • magfr's frustration with OID registrations and his hopefully-this-time solution proposal
    • TrogL's multi-core CPU monitoring
  • Testing infrastructure and supported releases
    • Wes' proposal from a few meetings ago
    • Magfr: need a robust C-code based test system
  • Future Directions
  • Other Issues
  • Round Table