Thanks Dima! That definitely would be handy. -Mikhail
On Mon, Apr 3, 2017 at 10:55 PM, Dima Spivak <[email protected]> wrote: > I can help with running the API compatibility tooling. It's the least I can > do since I no longer have access to the computing resources I used to rely > upon for testing releases. Just ping me when you need a hand, Mikhail. > > On Mon, Apr 3, 2017 at 10:35 PM Mikhail Antonov <[email protected]> > wrote: > > > Hi, > > > > I've been planning to cut an RC for 1.3.1 for some time, apologize for > the > > delay here. I'm going to go over outstanding jiras tomorrow, > > I think there are still few issues waiting for backports. > > > > Andrew - appreciate your offer! I have started preparations for 1.3.1 > > release, but any help with triaging changes, API compatibility tests > > and general release testing would definitely be helpful. > > > > Thanks! > > -Mikhail > > > > On Mon, Apr 3, 2017 at 9:52 PM, Andrew Purtell <[email protected] > > > > wrote: > > > > > I'd be happy to RM 1.3.1 unless someone already has it waiting in the > > > wings. > > > > > > > > > > On Apr 3, 2017, at 5:43 PM, James Taylor <[email protected]> > > wrote: > > > > > > > > Hello, > > > > We'd like to start supporting releases of Phoenix that work with the > > > HBase > > > > 1.3 branch, but there's a committed fix on which we rely > (HBASE-17587) > > > for > > > > Phoenix to function correctly. Is there a time frame for an HBase > 1.3.1 > > > > release? > > > > Thanks, > > > > James > > > > > > > > > > > -- > > Thanks, > > Michael Antonov > > > -- > -Dima > -- Thanks, Michael Antonov
