Difference between revisions of "Notes20121022"

From Net-SNMP Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<!-- Reminder for Fall to Spring - use "time=20" for end of DST, and for Spring to Fall use "time=19"  -->
 
<!-- Reminder for Fall to Spring - use "time=20" for end of DST, and for Spring to Fall use "time=19"  -->
 
<!-- US Daylight savings times: http://www.timetemperature.com/tzus/daylight_saving_time.shtml -->
 
<!-- US Daylight savings times: http://www.timetemperature.com/tzus/daylight_saving_time.shtml -->
{{meetingtime|time=19|year=2012|month=10|day=22|nextyear=2012|nextmonth=11|nextday=??|prevyear=2012|prevmonth=09|prevday=10}}
+
{{meetingtime|time=19|year=2012|month=10|day=22|nextyear=2013|nextmonth=01|nextday=07|prevyear=2012|prevmonth=09|prevday=10}}
  
 
* Next Date
 
* Next Date
Line 10: Line 10:
 
** Next up: '''from 20120723: concentrate on patches/bugs instead of a release'''
 
** Next up: '''from 20120723: concentrate on patches/bugs instead of a release'''
 
* Administrative
 
* Administrative
** wiki issues
+
** PERSIST until fixed: wiki issues
 
*** '''mostly fixed now; confirmededit (ie, captchas) so the login page is broken'''
 
*** '''mostly fixed now; confirmededit (ie, captchas) so the login page is broken'''
 
*** '''during the 30 minutes of off time, 4 spam accounts were created'''
 
*** '''during the 30 minutes of off time, 4 spam accounts were created'''
Line 24: Line 24:
 
*** '''some discussion about how old releases are a pain in the first place'''
 
*** '''some discussion about how old releases are a pain in the first place'''
 
* Technical
 
* Technical
** Time kill off redundant modules?
+
** PERSIST: Time kill off redundant modules?
 
*** notes on things that may need (re)moving:
 
*** notes on things that may need (re)moving:
 
**** ucd-snmp/lmSensors <> ucd-snmp/lmsensorsMib
 
**** ucd-snmp/lmSensors <> ucd-snmp/lmsensorsMib
Line 38: Line 38:
 
**** '''hardaker: the goal was to have newer code "stage" but the reality is that's a pain.  We shouldn't be making users have to know.  *we* should have the pain.  Thus, when we rewrite I think the right thing to do is rewrite in place and optionally move the older code to obsolete/ so that it can be activated if the newer code fails.'''
 
**** '''hardaker: the goal was to have newer code "stage" but the reality is that's a pain.  We shouldn't be making users have to know.  *we* should have the pain.  Thus, when we rewrite I think the right thing to do is rewrite in place and optionally move the older code to obsolete/ so that it can be activated if the newer code fails.'''
 
* Roundtable
 
* Roundtable
 +
** me: coordinating allura, bugs?, and unknown
 +
** trogl: hopefully more oracle/sun gear to work on soon.

Latest revision as of 14:30, 30 November 2012

Previous: 2012-09-10
Next: 2013-01-07

This is the meeting agenda/notes for the Meeting held on 2012-10-22.

Date and Time: 2012-10-22 19:00 UTC

  • Next Date
    • Nov 26th
  • Releases
    • 5.7.2 -- Wes
      • is out the door
    • Next up: from 20120723: concentrate on patches/bugs instead of a release
  • Administrative
    • PERSIST until fixed: wiki issues
      • mostly fixed now; confirmededit (ie, captchas) so the login page is broken
      • during the 30 minutes of off time, 4 spam accounts were created
    • Wiki Main Page
      • good: remove from future agendas
    • PERSIST: Switch to Allura?
      • rough consensus to switch
      • announce with switch in 2 weeks?
    • PERSIST: Adding a "this is an old release" header to the README and other files for older branches?
      • consensus to add a note
      • consider adding a runtime or configure time check?
        • runtime: daemons
      • some discussion about how old releases are a pain in the first place
  • Technical
    • PERSIST: Time kill off redundant modules?
      • notes on things that may need (re)moving:
        • ucd-snmp/lmSensors <> ucd-snmp/lmsensorsMib
        • ucd-snmp/memory_XXX <> hardware/data_acces/memory_xxx
        • disman/expression <> disman/expression-mib (which is better)?
        • disman/event <> disman/event-mib (which is better)?
        • mibII/ipCidrRouteTable <> ip-forward-mib/ipCidrRouteTable
      • Conclusions from the discussion:
        • good idea in general
        • needs a wider discussion on -coders
        • move to an obsolete/ folder for a release on two
        • some unresolved discussions about weather and how-to warn about new versions
        • hardaker: the goal was to have newer code "stage" but the reality is that's a pain. We shouldn't be making users have to know. *we* should have the pain. Thus, when we rewrite I think the right thing to do is rewrite in place and optionally move the older code to obsolete/ so that it can be activated if the newer code fails.
  • Roundtable
    • me: coordinating allura, bugs?, and unknown
    • trogl: hopefully more oracle/sun gear to work on soon.