Another option is to go ahead and break backwards compatibility, and if
anyone complains we can backport bug fixes for them to the 0.9.x release
branch.  My gut is that this will be way less work.

- Dan

On Wed, Jun 1, 2016 at 12:28 PM, Mike Percy <mpe...@apache.org> wrote:

> On Wed, Jun 1, 2016 at 11:56 AM, Jean-Daniel Cryans <jdcry...@apache.org>
> wrote:
>
> > So, in your opinion Mike, should we do the change if PODLINGNAMESEARCH-93
> > is solved within a reasonable time frame before 1.0?
> >
>
> I think we should do it in a backwards compatible way, deprecate the old
> names, and delete them after a couple of releases. If it's just a few hours
> of someone's time then I think it's a no brainer to just do a facade.
>
> That said, if we're talking a week or weeks of work to do it right then I'm
> +0 to renaming and breaking backcompat before 1.0 and -0 for leaving them
> not renamed for the forseeable future. I haven't tried to scope the effort.
>
> Mike
>

Reply via email to