| Re: [epsilon-dev] Proposal to remove deprecated methods |
Hi Dimitris, Thank you for your thoughts. This was my reasoning too: although most of the changes to Epsilon have been additions, enhancements and bug fixes, it’s probably substantial enough to be part of a major release and so an ideal opportunity to clean up some of the legacy API. Though I’m not sure if a major release entails more administrative overhead. Speaking of which, what is the timescale for releases? Looking at the history it seems to be every 1-2 years and 1.5 was released in August 2018, though presumably there aren’t any hard constraints on the schedule. Thanks, Sina
Hi Sina,Removing deprecated methods typically requires a new major version(i.e. 2.0). Having said this, with the amount of work that has goneinto Epsilon since 1.5.1 and given other changes in the API, what wecall 1.6 feels more like 2.0 anyway so perhaps we should bump up themajor version and think about making a 2.0 release.Thanks,DimitrisOn Sat, 12 Oct 2019 at 15:17, Sina Madani <sinadoom@xxxxxxxxxxxxxx> wrote:>> Hi everyone,>>>> I was wondering whether it would be a good time to remove deprecated methods? If so are there any methods (or classes) to be wary of in doing so? I presume most deprecations were in place before the release of 1.5, giving users one releaseâ notice before removal.>>>> Thanks,>> Sina>>>> _______________________________________________> epsilon-dev mailing list> epsilon-dev@xxxxxxxxxxx> To change your delivery options, retrieve your password, or unsubscribe from this list, visit> https://www.eclipse.org/mailman/listinfo/epsilon-dev-- Dimitris KolovosProfessor of Software EngineeringDepartment of Computer ScienceUniversity of Yorkhttp://www.cs.york.ac.uk/~dkolovosEMAIL DISCLAIMER http://www.york.ac.uk/docs/disclaimer/email.htm |
