IMHO, this bug is serious enough to be a showstopper. There's no workaround
for it in depent projects such as Phoenix. How about we roll another RC
with a fix today?
Other non Apache projects don't need to wait until the release closes (or
could even rely on non released bits).
James
On Mon,
Hey James,
There are other projects that depend on the 0.11.0 release, and need it in
the next couple of days. This bug can be worked around in the dependent
projects.
I suggest letting this release go through by marking TEPHRA-223 as a known
issue. We can do a 0.11.1 release immediately after fi
Looks like a serious issue was found with TEPHRA-223, so switching my vote
to -1. Hopefully we can get a quick fix with a new RC very soon.
James
On Fri, Feb 17, 2017 at 12:12 PM, Alan Gates wrote:
> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Feb 17, 2017, at 11:52 AM, James Tay
Forwarding my +1 from the dev list.
Alan.
> On Feb 17, 2017, at 11:52 AM, James Taylor wrote:
>
> Transferring my +1 from the dev list vote over here.
>
> On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran
> wrote:
>
>> Hi all,
>>
>> This is a call for a vote on releasing Apache Tephra 0.1
Transferring my +1 from the dev list vote over here.
On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran
wrote:
> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> release candidate 1. This is the fourth release of Tephra.
>
> Apache Tephra community has voted
