I'd propose the following: fields will be removed no less than 90 days and
1 release after they have been deprecated. This might be a little bit
conservative w.r.t to days, so feel free to push back if you think, e.g.,
60 days is more reasonable.

On Mon, Feb 1, 2016 at 2:35 PM, Bill Farner <wfar...@apache.org> wrote:

> Sounds reasonable.  Can you firm up the proposal and apply numbers?
>
> On Mon, Feb 1, 2016 at 12:09 PM, Joshua Cohen <jco...@apache.org> wrote:
>
> > This came up briefly last week, and we also discussed in the IRC meeting
> > today. Given the increased release cadence, I think we would benefit from
> > moving from release-based deprecation to time-based. That is to say,
> > instead of deprecating in release X and removing release X+1, we would
> > deprecate in release X and remove no less than N later and at least M
> > releases later.
> >
> > General consensus in the IRC meeting was in favor, however I wanted to
> > start a thread to discuss to gather additional feedback and if everyone
> is
> > in agreement, then we can solidify the actual details on what the new
> > deprecation policy should be.
> >
> > Cheers,
> >
> > Joshua
> >
>

Reply via email to