[ 
https://issues.apache.org/jira/browse/OFBIZ-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830072#comment-16830072
 ] 

Pierre Smits commented on OFBIZ-10999:
--------------------------------------

Jacques,

What was the gist of the discussion back then? There were a lot of follow-up 
suggestions (actionable items?), but were they followed up/through?

The thing is that we have about 200 functions marked deprecated, and easy way 
of telling when they were deprecated or when they will be removed.

> Have all @deprecated show when it will be removed from the repo
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-10999
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10999
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Priority: Major
>
> Currently we don't provide any information on functions with @deprecated when 
> they will be removed from the repo.
> I suggest we add a 'Will be removed at ' + a designator for a release branch 
> after the latest available to the @deprecated, when a function is to be 
> deprecated.
> As an example:
>  * Currently latest available branch is: release18.12
>  * if a contributor deprecates a function now, the statement would be: 
> @deprecated Will be removed at release branch 20.12
> This would leave adopters with enough time to plan for migrations, and at the 
> moment the new branch is cut contributors can easily find what needs to be 
> removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to