On Mar 23, 2010, at 4:52 PM, Martin Englund wrote:
When is it acceptable to introduce an incompatible change to a type?
Due to a change in Solaris zone creation, the use of the ip property
has become ambiguous. Formerly you has to supply both interface name
and ip address when you created a zone (separated by a ":"), but with
zone exclusive IP stacks, you only have to supply the interface name
(and then plumb the interface with an IP from within the zone).
Reusing the ip property in this case will be confusing, as it will
only hold the interface name. I propose to extract the interface name
from the ip property and use an interface property instead.
This will break current configurations:
1) the ip property does not contain a valid ip address
2) the zone type does not contain an interface property
So my question is: when is it acceptable to introduce this kind of
change?
I'd say in rowlf - we're not actively planning on breaking a lot in
it, but I'm confident we'll be doing some non-backward-compatible
things, and in general, the full feature releases are the time to do
this kind of breakage.
--
A computer lets you make more mistakes faster than any invention in
human history--with the possible exceptions of handguns and tequila.
-- Mitch Ratcliffe
---------------------------------------------------------------------
Luke Kanies -|- http://reductivelabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
