I completely misread, don't pay attention to my comment. JV.
On Thu, Jan 13, 2011 at 2:40 PM, Vincent Massol <[email protected]> wrote: > > On Jan 13, 2011, at 2:22 PM, Jean-Vincent Drean wrote: > >> On Thu, Jan 13, 2011 at 1:13 PM, Vincent Massol <[email protected]> wrote: >>> Hi devs, >>> >>> I think the start of the XE 3.x cycle is a good time to remove some >>> deprecated methods/classes. >>> >>> We have a deprecation strategy defined already: >>> http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HDeprecationStrategy >>> >>> " >>> Our rule is to keep @deprecated methods/classes for 2 final releases after >>> the version where they were first added has been released as final. >>> >>> For example if a method is deprecated in, say XE 1.3M2 then the method will >>> be removed in 1.6M1 or after. Of course any major new release can deprecate >>> anything. For example a XWiki 2.0 release is allowed to break backward >>> compatibility (obviously we need to be careful to offer a migration path >>> for users of previous major versions). >>> " >>> >>> So 2 final releases mean that deprecations introduced in 2.5.x or before >>> can theoretically be removed for XE 3.0 final. >>> >>> However, IMO we shouldn't remove deprecated methods/classes that are public >>> for scrips since this will break xwiki users. >>> >>> Are we ok to do that? >>> >> >> I agree with Caleb that we should obey our rule and remove deprecation >> introduced in 2.4.x and before (3 majors). > > I don't think Caleb mentioned 2.4.x. Why not follow our rule and say 2.5.x? > Are you proposing to change our rules to 3 final releases rather than 2? > > Thanks > -Vincent > >> Otherwise +1. >> >> Thanks, >> JV. > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
