All stuff from tracker/list changes MUST be done through
this
Long discussion surrounding what levels go into which
files; dts12 will write up short descriptive text about it
Change discussions on -coders and subject line formatting
suggestion: rNNN number *and* author minimum; preferably
also a subject description
No objections
Backwards compatibility discussion (hint; I'm gonna say it's a
MUST)
Existing Policy Reminder
Delete interfaces and accessible variables only when
beneficial
They get marked as deprecated for *2* major releases
before being removed
Functionality of existing interfaces can't be changed;
only new ones created
(the old can be a wrapper around the new if need be,
thuogh)
Wes describes past reasoning behind current policy
Thoughts on the current policy:
magfr: Good
dts12: The basic policy is good. At some point we
might need to look at more significant jump (a la the v5
agent reworking). That would most naturally be released
as v6.0
bartvanassche: Changes for a project with many users
must be small and incremental, otherwise no one is going
to risk an upgrade.
Coding Issues
magfr's frustration with OID registrations and his
hopefully-this-time solution proposal