Re: [VOTE] HTrace-4.3.0-incubating RC3
A question about protocol here... Two of the votes have come in past the deadline, but without them we wouldn't have had enough votes to get quorum on the release. Can we still accept them and move forward, or do we need to start over with a new vote? I'd really like to avoid the second option since getting enough votes here has been tenuous. I'm also making a note for myself for future votes that seven days is probably a better window than five. Mike On Tue, May 23, 2017 at 7:36 PM, Colin McCabe wrote: > +1 > > Verified checksums > Build from source using Maven 3.0.4 (with -Pnative) > Successfully ran unit tests > > > > On Mon, May 22, 2017, at 01:18, Elliott Clark wrote: > > +1 > > > > verified signatures. > > build from source. > > Checked that everything looked to be in the correct locations. > > > > On Sun, May 21, 2017 at 3:49 PM, Masatake Iwasaki < > > iwasak...@oss.nttdata.co.jp> wrote: > > > > > +1 > > > > > > * verified signature and mds. > > > * built and installed from source tarball by maven-3.0.4. > > > * built hadoop trunk against htrace-4.3.0-incubating. > > > * verified that spans in HDFS works by HTracedSpanReceiver and htraced. > > > > > > Thanks, > > > Masatake Iwasaki > > > > > > > > > On 5/17/17 05:40, Mike Drob wrote: > > > > > >> Hi Devs, > > >> > > >> Please consider the following release candidate for Apache HTrace > > >> 4.3.0-incubating! > > >> > > >> http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/ > > >> > > >> The jars have been staged here: > > >> > > >> https://repository.apache.org/content/repositories/ > orgapachehtrace-1029 > > >> > > >> There's a few minor fixes in this release: > > >> > > >> ** Bug > > >> * [HTRACE-387] - htrace-c should have a test dependency on htrace > > >> -htraced > > >> * [HTRACE-393] - Binary annotations are being shown as base64 in > the > > >> zipkin frontend > > >> * [HTRACE-398] - Enforce requirement to build with Maven 3.0.4 > from > > >> HTRACE-236 > > >> > > >> ** Improvement > > >> * [HTRACE-386] - htrace-c: add functions for retrieving the span > ID > > >> to > > >> the public API > > >> > > >> RC History: > > >> RC0 - Discarded due to user error. > > >> RC1 - Missing some version string updates, vote failed. > > >> RC2 - Discarded due to missing HTRACE-398 > > >> RC3 - Current > > >> > > >> This vote will run for 5 days ( Sun May 21 21:30:00 UTC 2017 ) > > >> > > >> Thanks, > > >> Mike > > >> > > >> > > > >
Re: [VOTE] HTrace-4.3.0-incubating RC3
+1 Verified checksums Build from source using Maven 3.0.4 (with -Pnative) Successfully ran unit tests On Mon, May 22, 2017, at 01:18, Elliott Clark wrote: > +1 > > verified signatures. > build from source. > Checked that everything looked to be in the correct locations. > > On Sun, May 21, 2017 at 3:49 PM, Masatake Iwasaki < > iwasak...@oss.nttdata.co.jp> wrote: > > > +1 > > > > * verified signature and mds. > > * built and installed from source tarball by maven-3.0.4. > > * built hadoop trunk against htrace-4.3.0-incubating. > > * verified that spans in HDFS works by HTracedSpanReceiver and htraced. > > > > Thanks, > > Masatake Iwasaki > > > > > > On 5/17/17 05:40, Mike Drob wrote: > > > >> Hi Devs, > >> > >> Please consider the following release candidate for Apache HTrace > >> 4.3.0-incubating! > >> > >> http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/ > >> > >> The jars have been staged here: > >> > >> https://repository.apache.org/content/repositories/orgapachehtrace-1029 > >> > >> There's a few minor fixes in this release: > >> > >> ** Bug > >> * [HTRACE-387] - htrace-c should have a test dependency on htrace > >> -htraced > >> * [HTRACE-393] - Binary annotations are being shown as base64 in the > >> zipkin frontend > >> * [HTRACE-398] - Enforce requirement to build with Maven 3.0.4 from > >> HTRACE-236 > >> > >> ** Improvement > >> * [HTRACE-386] - htrace-c: add functions for retrieving the span ID > >> to > >> the public API > >> > >> RC History: > >> RC0 - Discarded due to user error. > >> RC1 - Missing some version string updates, vote failed. > >> RC2 - Discarded due to missing HTRACE-398 > >> RC3 - Current > >> > >> This vote will run for 5 days ( Sun May 21 21:30:00 UTC 2017 ) > >> > >> Thanks, > >> Mike > >> > >> > >
Podling Report Reminder - June 2017
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 June 2017, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, June 07). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/June2017 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
