Difference between revisions of "Notes20071114"
From Net-SNMP Wiki
| (10 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Administrative Meetings]] | + | This is the meeting minutes and agenda for the [[Administrative Meetings|Meeting]] on 2007-11-14. |
| + | Date and Time: [http://www.timeanddate.com/worldclock/fixedtime.html?year=2007&month=11&day=14&hour=21&min=0&sec=0&sort=2 November 14th 21:00 UTC]? | ||
| + | |||
| + | Agenda: | ||
* Next meeting date (Wes) | * Next meeting date (Wes) | ||
| + | *: ''December 11th'' | ||
* status reports | * status reports | ||
** 5.3.2 (TrogL) | ** 5.3.2 (TrogL) | ||
| + | **: ''[Not present]'' | ||
** user support load | ** user support load | ||
*** wiki answer categories and mail documentation system (Wes) | *** wiki answer categories and mail documentation system (Wes) | ||
| + | **** general consensus: good, but may be harder when it gets larger | ||
| + | **** ''needed: good answer and tutorial mixing'' | ||
| + | **** ''(13:05:37) hardaker: the difference between a good answer, a faq answer and a tutorial answer is only how you get there. The user needs the information and currently has 3 places to look for it (which is bad). A good category hierarchy should let them get there without knowing which section it's in.'' | ||
| + | **** ''dts12 will put something in place'' | ||
| + | <tasks> | ||
| + | [2] ''Extend categorisation to Tutorials/FAQ'' (dts12) | ||
| + | </tasks> | ||
** makerelease (Wes) | ** makerelease (Wes) | ||
| + | **: ''Active as an S/F project, and in use on other packages'' | ||
| + | **: ''Adopt for the next release (post 5.3.2)'' | ||
** lmsensors rewrite (dave) | ** lmsensors rewrite (dave) | ||
| + | **: ''Done - awaiting reactions'' | ||
** coverity (Wes) | ** coverity (Wes) | ||
| + | **: ''No progress'' | ||
| + | * Coding issues | ||
| + | ** instance handler API (Magnus) | ||
| + | **: See thread [http://marc.info/?t=119308653300001&r=1&w=4|"Removing functions"] in coders (22/23 Oct) | ||
| + | **: ''Keep existing registration calls'' | ||
| + | **: ''Mark internal handlers as deprecated for 5.5 - consider dropping them for 5.6'' | ||
| + | ** multiple 5.4.1 container-related crash reports: roadmap to solution? | ||
| + | **: ''No report'' | ||
| + | <tasks> | ||
| + | [1] ''Need to tackle this properly'' (rstory) | ||
| + | </tasks> | ||
* next release? (rstory) | * next release? (rstory) | ||
| − | ** 5.2. | + | ** 5.2.5? |
| + | ***: ''Pause after 5.3.2 is out, to allow the application of outstanding bug fixes.'' | ||
| + | ***: ''Then look to release 5.2.5 over Christmas/New Year.'' | ||
| + | ***: ''Ideally in parallel with a blitz on the bug tracker, ready for addressing 5.4.2 in early 2008'' | ||
Latest revision as of 23:51, 15 November 2007
This is the meeting minutes and agenda for the Meeting on 2007-11-14.
Date and Time: November 14th 21:00 UTC?
Agenda:
- Next meeting date (Wes)
- December 11th
- status reports
- 5.3.2 (TrogL)
- [Not present]
- user support load
- wiki answer categories and mail documentation system (Wes)
- general consensus: good, but may be harder when it gets larger
- needed: good answer and tutorial mixing
- (13:05:37) hardaker: the difference between a good answer, a faq answer and a tutorial answer is only how you get there. The user needs the information and currently has 3 places to look for it (which is bad). A good category hierarchy should let them get there without knowing which section it's in.
- dts12 will put something in place
- wiki answer categories and mail documentation system (Wes)
- 5.3.2 (TrogL)
<tasks> [2] Extend categorisation to Tutorials/FAQ (dts12) </tasks>
- makerelease (Wes)
- Active as an S/F project, and in use on other packages
- Adopt for the next release (post 5.3.2)
- lmsensors rewrite (dave)
- Done - awaiting reactions
- coverity (Wes)
- No progress
- makerelease (Wes)
- Coding issues
- instance handler API (Magnus)
- See thread "Removing functions" in coders (22/23 Oct)
- Keep existing registration calls
- Mark internal handlers as deprecated for 5.5 - consider dropping them for 5.6
- multiple 5.4.1 container-related crash reports: roadmap to solution?
- No report
- instance handler API (Magnus)
<tasks> [1] Need to tackle this properly (rstory) </tasks>
- next release? (rstory)
- 5.2.5?
- Pause after 5.3.2 is out, to allow the application of outstanding bug fixes.
- Then look to release 5.2.5 over Christmas/New Year.
- Ideally in parallel with a blitz on the bug tracker, ready for addressing 5.4.2 in early 2008
- 5.2.5?
