The point of marking API's as deprecated is to indicate that they should
not be used, so by definition it's a suggestion to upgrade.

But importantly, it's a suggestion since it will co-exist with the new API.
I suppose you could create a maintenance branch where bugfixes will go, but
I see it as quite unlikely that serious efforts would be expended on these
branches (save for "absolutely critical" bugfixes) given that a new API has
been introduced.

Alternatively, bugfixes to deprecated APIs could be applied as long the the
deprecated API exists in the codebase. But at one point, I think the
deprecated API is meant to tbe removed. Maybe this is the point where a
maintenance branch could be created?



On Fri, Jan 1, 2016 at 5:22 AM, Egon Willighagen <egon.willigha...@gmail.com
> wrote:

> On Thu, Dec 31, 2015 at 8:16 PM, Rajarshi Guha <rajarshi.g...@gmail.com>
> wrote:
> > On Thu, Dec 31, 2015 at 6:21 AM, John M <john.wilkinson...@gmail.com>
> wrote:
> > As to Egons concern regarding maintenance burden - I think it's a safe to
> > state that deprecated API's will not be maintained.
>
> That does not sound consistent... one one hand you want to keep the
> API stable, so that people do not have to migrate (immediately), but
> at the same time say they must upgrade because the code is no longer
> maintained... that does not make sense to me...
>
> Egon
>
> PS. sending an email to cdk-user@ about the code migration things I
> wrote over the past few years in the wiki:
> https://github.com/cdk/cdk/wiki/Migration
>
> --
> E.L. Willighagen
> Department of Bioinformatics - BiGCaT
> Maastricht University (http://www.bigcat.unimaas.nl/)
> Homepage: http://egonw.github.com/
> LinkedIn: http://se.linkedin.com/in/egonw
> Blog: http://chem-bla-ics.blogspot.com/
> PubList: http://www.citeulike.org/user/egonw/tag/papers
> ORCID: 0000-0001-7542-0286
> ImpactStory: https://impactstory.org/EgonWillighagen
>



-- 
Rajarshi Guha | http://blog.rguha.net
NIH Center for Advancing Translational Science
------------------------------------------------------------------------------
_______________________________________________
Cdk-user mailing list
Cdk-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdk-user

Reply via email to