On Wed, Feb 15, 2012 at 10:35 PM, Amila Jayasekara <[email protected]> wrote:
> Hi All, > > Since next release is going to be a major carbon release (4.0.0), is > it ok to change interface classes ? (without deprecating them) > Well, the proper fix should always deprecate the existing and add the improved functionality on top of that. Are we talking about addition intyerface elements into this here, or replacing? I assume it is replacing, and if that is the case, how about marking the existing deprecated and adding the proper ones side by side? The proper way to do this in the future would be to mark them as deprecated in the point releases and get them removed in major release. Note that, unlike in the past, we also need to think about migration efforts when we do releases now. It does not mean that the new improvements need to be blocked by backward compatibility for the sake of migration. Rather we need to define a strategy in terms of migration, if one thinks migration applies. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
