Difference between revisions of "Notes20101011"

From Net-SNMP Wiki
Jump to: navigation, search
Line 36: Line 36:
 
*** '''policy stays the same.  We as a group need to enforce them.'''
 
*** '''policy stays the same.  We as a group need to enforce them.'''
 
*** '''we'll switch to 1-week turn arounds for preN)'''
 
*** '''we'll switch to 1-week turn arounds for preN)'''
 +
**** '''if no changes since the last preN then likely do a rc1'''
 
* Technical
 
* Technical
 
** Future and continual discussion topics
 
** Future and continual discussion topics

Revision as of 19:55, 11 October 2010

Previous: 2010-09-20
Next: 2010-11-29

This is the meeting agenda/notes for the Meeting held on 2010-10-11.

Date and Time: 2010-10-11 19:00 UTC


Agenda

  • Next Meeting Date
    • November 29th
  • Releases
    • 5.6
      • Wes released 5.6 but there are a couple of immediate problems
      • Future plans for branching and 5.6.1, etc.
        • patches tree created for 5.6
        • will release 5.6.1 in december
        • will do in parallel with 5.5.1 due in Jan
      • Upload permissions
        • dts12: Just a quick note - when creating a release directory, please make sure it's group writable.
        • the mkdir should possibly go into the release script?
      • Binary Release instructions (Release_Instructions)
        • please please please document what you do. The big ones in my mind are solaris and win32.
        • Include flags used to build with features
      • Binary Release MIB modules (e.g. examples)
        • what MIB modules are/should be included in binary releases?
        • stew till next time
        • document choices in Release Instructions though
    • Next branch to target?
      • 5.5.1 in January
      • 5.3.4 after that, probably feb or mar
  • Administrative
    • Release Policy (http://www.net-snmp.org/dev/release-policy.html)
      • rcN series generally goes well
      • preN series is generally ignored in terms of the guidelines; this needs to be fixed
      • turn around times for a release are far too long
      • branch should still be created at final
      • pre-release series *must* get more locked down
      • policy stays the same. We as a group need to enforce them.
      • we'll switch to 1-week turn arounds for preN)
        • if no changes since the last preN then likely do a rc1
  • Technical
    • Future and continual discussion topics
      • testing infrastructure and unit tests
      • build cmake vs ??
      • streamlined/stripped-down library and agent
  • Round Table