forked from hardaker/net-snmp
-
Notifications
You must be signed in to change notification settings - Fork 2
Notes20101011
Bill Fenner edited this page Aug 30, 2018
·
1 revision
- 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
- 5.6
- 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
- Release Policy (http://www.net-snmp.org/dev/release-policy.html)
- Technical
- Future and continual discussion topics
-
Testing Infrastructure
and unit tests
- Wes will try to write up more docs and examples
- Will be a longer topic next time
- please study and review
- build cmake vs ??
- streamlined/stripped-down library and agent
-
Testing Infrastructure
and unit tests
- Future and continual discussion topics
- Round Table
- Wes: a reduced and stream-lined code, along with a read-only agent