Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0E350200B82 for ; Fri, 2 Sep 2016 02:43:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0CAAA160AB7; Fri, 2 Sep 2016 00:43:13 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 53719160AB5 for ; Fri, 2 Sep 2016 02:43:12 +0200 (CEST) Received: (qmail 22722 invoked by uid 500); 2 Sep 2016 00:43:11 -0000 Mailing-List: contact dev-help@htrace.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@htrace.incubator.apache.org Delivered-To: mailing list dev@htrace.incubator.apache.org Received: (qmail 22711 invoked by uid 99); 2 Sep 2016 00:43:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2016 00:43:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 077A8CB82E for ; Fri, 2 Sep 2016 00:43:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.539 X-Spam-Level: X-Spam-Status: No, score=-4.539 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.519] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id EhKa647TN8PO for ; Fri, 2 Sep 2016 00:43:09 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id D26E760D9E for ; Fri, 2 Sep 2016 00:43:08 +0000 (UTC) Received: (qmail 22695 invoked by uid 99); 2 Sep 2016 00:43:08 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2016 00:43:08 +0000 Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 0B7DB1A0284 for ; Fri, 2 Sep 2016 00:43:07 +0000 (UTC) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailauth.nyi.internal (Postfix) with ESMTP id 72A7A203C4 for ; Thu, 1 Sep 2016 20:43:06 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute1.internal (MEProxy); Thu, 01 Sep 2016 20:43:06 -0400 Received: by mailuser.nyi.internal (Postfix, from userid 99) id 4B8C696C23; Thu, 1 Sep 2016 20:43:06 -0400 (EDT) Message-Id: <1472776986.1013090.713345065.37743025@webmail.messagingengine.com> X-Sasl-Enc: hSikcrEQX6z8+m4hvc8ZKrZHziRu2wDE9lU/VtJcaNiQ 1472776986 From: Colin McCabe To: dev@htrace.incubator.apache.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-8baf8b60 Subject: Re: Time for another release? Date: Thu, 01 Sep 2016 17:43:06 -0700 In-Reply-To: References: <1472237662.3648818.707254929.3884CE76@webmail.messagingengine.com> archived-at: Fri, 02 Sep 2016 00:43:13 -0000 Thanks for pushing on this. We definitely should do a release soon. I agree that what's in master now should be pretty stable. Maybe we should do a quick scrub to see if there are any more open LICENSE or NOTICE issues remaining in JIRA. If you want to RM (release manager), Stack put up some notes here, based on the last few releases: http://htrace.incubator.apache.org/building.html . It's generated from the markdown file at ./src/main/site/markdown/building.md (probably should be renamed to release.md...) Also, I think the process changed so that we're now checking source tarballs into svn, rather than doing the rsync like it says there. best, Colin On Thu, Sep 1, 2016, at 14:40, Mike Drob wrote: > What else can I do to help drive this? > > I'm using this filter to look at pending issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D% > 20HTRACE%20AND%20%22Target%20Version%2Fs%22%20%3D%204.2%20AN > D%20status%20!%3D%20resolved%20ORDER%20BY%20priority%20ASC > > I have a patch up for HTRACE-346, and think that everything else could > feasibly be pushed to the next version. > > Mike > > > > On Fri, Aug 26, 2016 at 1:54 PM, Colin McCabe wrote: > > > On Fri, Aug 26, 2016, at 07:06, Mike Drob wrote: > > > HTrace devs, > > > > > > It's been a while since our last update, and it looks like there are > > > several good fixes slated for the 4.2 version. What do you all think > > > about > > > releasing soon? > > > > +1. > > > > > > > > There's a few issues that I think are close to wrapping up, or could be > > > included soon, but I didn't see any blockers in JIRA. The only question > > > in > > > my mind is how close we are on HTRACE-376 > > > . > > > > I think it's ready to submit. It makes HTrace more generally useful, > > extending it to use-cases where you need finer granularlity than > > milliseconds-- and it does it in a fully backwards-compatible way. The > > 4.2 release probably would go more smoothly if we bumped HTRACE-376 to > > 4.3, though. > > > > cheers, > > Colin > > > > > > > > Meanwhile, can somebody create a 4.3 version in JIRA so that incomplete > > > issues have a place to go? > > > > > > Thanks, > > > Mike > >