EdColeman commented on PR #2947:
URL: https://github.com/apache/accumulo/pull/2947#issuecomment-1253704710

   Would it make sense for 2.1 if both classes were marked as deprecated and 
then point to the replacement?
   
   I think the history was that the master version was / is deprecated because 
of the renaming to manager - I thought we were scheduled to fully remove master 
in 3.0 - but we need to leave some references in 2.1 because of semver?
   
   I think the ideal way to handle this would be to have them print a 
deprecated warning and then call the equivalent new functionality - this would 
preserve compatibility from anyone coming from 1.10.x or 2.0.x to 2.1.0.  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to