On Thu, Feb 16, 2012 at 7:34 AM, Samisa Abeysinghe <sam...@wso2.com> wrote: > > > On Wed, Feb 15, 2012 at 10:35 PM, Amila Jayasekara <ami...@wso2.com> 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.
Hi Samisa, Please find some comments inline. > > 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? In my re-factoring i need to do both. > > 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. I guess in that case i will extend the existing interface and add new methods and will deprecate replacing methods. Cos adding new methods to an interface will anyhow break existing code. > > 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. +1 Thanks AmilaJ > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Mobile : +94773330538 _______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
