Notes20121022 - fenner/net-snmp-wiki-experiment GitHub Wiki

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.