accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@cloudera.com>
Subject Re: Deprecation removal for 1.7.0
Date Mon, 06 Oct 2014 21:56:08 GMT
On Mon, Oct 6, 2014 at 4:51 PM, Christopher <ctubbsii@apache.org> wrote:

> On Mon, Oct 6, 2014 at 5:20 PM, Sean Busbey <busbey@cloudera.com> wrote:
>
> > On Mon, Oct 6, 2014 at 4:12 PM, Mike Drob <madrob@cloudera.com> wrote:
> >
> > >
> > >
> > > In general, I'm inclined to leave as much in as possible, and then if
> we
> > > must remove things then do so in 2.0.0. I know that our compatibility
> > > statement only promises one minor version, but that doesn't mean we
> have
> > to
> > > be strict at every opportunity.
> > >
> > > Mike
> > >
> > >
> >
> > Related, I'd like to EOL 1.5 shortly after 1.7 gets released. I don't
> want
> > to derail this thread with that discussion, but my guess is it's a much
> > easier sell if we're conservative about removing things. Just so everyone
> > knows where I'm coming from.
> >
> >
> >
> (+1 for EOL 1.5 after)
>
> In general, does this mean that you're okay with removing stuff deprecated
> prior to 1.5? With the exception of the instance.getConfiguration stuff,
> which was deprecated in 1.6.0 and I'd like to remove in 1.7.0, due to its
> problematic nature (requires further discussion), I could restrict the
> remaining cleanup to only stuff deprecated prior to 1.5.
>

For me, yeah that's the cut point I'd prefer to use. I'm hoping anyone who
did the move to 1.5 didn't move from a removed api to a deprecated API.

Maybe we should send a ping to user@ asking if any 1.5 users want to pipe
up about APIs they're using that were deprecated prior to 1.5?

-- 
Sean

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message