Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [VOTE] Release _timedlock API in 1.6.x?
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: <CACsi250ubiH=hQb3o+-c+kYiZ6O==hTHV_PyC7_f7LOTkXeuRA@mail.gmail.com>
Date: Mon, 22 May 2017 07:36:56 -0400
Cc: William A Rowe Jr <wrowe@rowe-clan.net>
Content-Transfer-Encoding: 7bit
Message-Id: <058AE446-E61D-4FC6-AF94-D07468986E3D@jaguNET.com>
References: <CACsi250ubiH=hQb3o+-c+kYiZ6O==hTHV_PyC7_f7LOTkXeuRA@mail.gmail.com>
To: APR Developer List <dev@apr.apache.org>
archived-at: Mon, 22 May 2017 11:37:13 -0000

I am conflicted... I'm still now sure what the real expected use-cases
are, and don't feel that it's quite solid/stable enough for inclusion.
But on the other hand, knowing the delays we have between API-changing
releases, NOT having it in 1.6 basically puts it to bed for a long,
long time, in case there *are* viable use cases for it.

I vote -0.9 (but am OK either way)

> On May 19, 2017, at 3:21 PM, William A Rowe Jr <wrowe@rowe-clan.net> wrote:
> 
> [  ] Release current svn _timedlock API implementation in 1.6
> 
> This seems to be the only questionable item remaining, and
> this vote (and an enhancement may be vetoed, AIUI) is very
> distinct from the poll on experimental features.
> 
> Please vote, thanks.