The lack of activity in this thread indicates to me a general disinterest in the subject by anyone willing to do the work to continue to preserve/fix/stabilize/maintain mock. As such, I think we should proceed to deprecated it for 1.8, as that seems to be the general desire by people who have expressed a willingness to do the work. I've created ACCUMULO-3920 to get it done.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, Jun 9, 2015 at 7:19 PM, Josh Elser <[email protected]> wrote: > Keith Turner wrote: >>>> >>>> > > +1 >>>> > > >>>> > > It should be deprecated ASAP inorder to clearly communicate its >>>> > status as >>>> > > unmaintained. If its deprecated in 1.8, its eligible to be >>>> > dropped in >>> >>> > 2.0 >>>> >>>> > > but does not have to be dropped. When its dropped can be a >>>> > separate >>>> > > decision. >>>> > > >>> >>> > >>> > Doesn't semver require a major version of deprecation? Still def >>> > deprecate >>> > immediately, remove eventually. >>> > >> >> >> No. Christopher had proposed that more strict requirement, but we >> eventually just went w/ unmodified semver. The following is from the >> semver page. >> >> >> Before you completely remove the functionality in a new major release >> there should be at least one minor release that contains the deprecation >> so >> that users can smoothly transition to the new API. >> > > Ok, cool. Thanks for the clarification. Was on my mobile and didn't have the > official docs handy to double check :)
