On Thu, Nov 14, 2013 at 3:47 PM, Sean Busbey <[email protected]>wrote:
> On Thu, Nov 14, 2013 at 2:41 PM, Keith Turner <[email protected]> wrote: > >> Should we deprecate mock accumulo for 1.6.0? This was considered [1] for >> 1.5.0. I started thinking about this because I never added conditional >> writer to mock. >> >> [1] : https://issues.apache.org/jira/browse/ACCUMULO-878 >> > > > Would deprecating it in 1.6.0 mean it is removed in 1.7.0 or in 1.8.0? > We do not have a good policy for deciding when deprecated things will be removed. I was looking at some other Java project today that declared when deprecated methods would be removed. > > Does it impact anything else? Would we not attempt feature parity for > 1.6.0 (e.g. conditional writer)? > Thats what I was thinking. If its deprecated then there is no need to add conditional writer support. > > > -- > Sean >
