Difference between revisions of "Notes20120116"
From Net-SNMP Wiki
m (... is makin livin haaard...) |
|||
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
<!-- Reminder for Spring 2012 - will need to use "time=20" to allow for DST --> | <!-- Reminder for Spring 2012 - will need to use "time=20" to allow for DST --> | ||
− | {{meetingtime|time= | + | {{meetingtime|time=20|year=2012|month=01|day=16|nextyear=2012|nextmonth=02|nextday=27|prevyear=2011|prevmonth=12|prevday=19}} |
* Next Date | * Next Date | ||
Line 8: | Line 8: | ||
*** '''dts12 hopes to start after this meeting''' | *** '''dts12 hopes to start after this meeting''' | ||
** 5.7 after that | ** 5.7 after that | ||
+ | *** '''hardaker start it after 5.5/5.6 is done(ish)''' | ||
* Administrative | * Administrative | ||
** Git | ** Git | ||
Line 23: | Line 24: | ||
***** '''remove''' | ***** '''remove''' | ||
** Google SOC | ** Google SOC | ||
+ | *** ''no comments received on the subject'' | ||
* Technical | * Technical | ||
** Coverity scan results | ** Coverity scan results | ||
+ | *** '''don't block a release from it, but useful stuff''' | ||
** --enable-read-only vs --disable-snmp-set | ** --enable-read-only vs --disable-snmp-set | ||
+ | *** understandable confusion between the two | ||
** DisMan Event MIB: monitoring string values | ** DisMan Event MIB: monitoring string values | ||
* Roundtable | * Roundtable |
Latest revision as of 19:13, 26 February 2012
Net-SNMP Meeting
2012-01-16
2012-01-16
Previous: | 2011-12-19 |
Next: | 2012-02-27 |
This is the meeting agenda/notes for the Meeting held on 2012-01-16.
Date and Time: 2012-01-16 20:00 UTC
- Next Date
- Feb 27th
- Releases
- 5.5/5.6 Starting Soon?
- dts12 hopes to start after this meeting
- 5.7 after that
- hardaker start it after 5.5/5.6 is done(ish)
- 5.5/5.6 Starting Soon?
- Administrative
- Git
- changelog generation
- hardaker created a new git log output that looks sufficient, using --no-merges...
- it may have issues on branches that don't yet have a tag though
- hardaker created a new git log output that looks sufficient, using --no-merges...
- NEWS/CHANGES
- hardaker's new script fixes improve it for pulling from the git log too
- email
- added --no-merges to the update hook
- seems fine, consensus wise, to drop these
- could show diffs, but I think that's too large
- nope
- summary at top of the list of refs: remove or keep?
- remove
- added --no-merges to the update hook
- changelog generation
- Google SOC
- no comments received on the subject
- Git
- Technical
- Coverity scan results
- don't block a release from it, but useful stuff
- --enable-read-only vs --disable-snmp-set
- understandable confusion between the two
- DisMan Event MIB: monitoring string values
- Coverity scan results
- Roundtable