From dev-return-354-archive-asf-public=cust-asf.ponee.io@zipkin.apache.org Mon Feb 11 03:02:29 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3AB9618064C for ; Mon, 11 Feb 2019 04:02:29 +0100 (CET) Received: (qmail 50396 invoked by uid 500); 11 Feb 2019 03:02:28 -0000 Mailing-List: contact dev-help@zipkin.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zipkin.apache.org Delivered-To: mailing list dev@zipkin.apache.org Received: (qmail 50383 invoked by uid 99); 11 Feb 2019 03:02:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2019 03:02:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C2CDF182410 for ; Mon, 11 Feb 2019 03:02:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.203 X-Spam-Level: X-Spam-Status: No, score=-0.203 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id RMnpidc65PsN for ; Mon, 11 Feb 2019 03:02:25 +0000 (UTC) Received: from mail-ot1-f47.google.com (mail-ot1-f47.google.com [209.85.210.47]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 5E89E60CE0 for ; Mon, 11 Feb 2019 03:02:25 +0000 (UTC) Received: by mail-ot1-f47.google.com with SMTP id w25so15056327otm.13 for ; Sun, 10 Feb 2019 19:02:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=UMCK9MP9WjwNZ9P0ZWCAplyXLZx/3TVtsoohDJUEWts=; b=ktb6HOWb34z4UAXKmaxXHq38nA6R9qkCyONopLfhQF6uFeLWk9HbPQbebGTg3STq5e H45mVLncmq4+z89ktSIM3AitIEhOPaxLX+jynbXdKfP4APsoP61N0OHeDGGvonbCl4Q1 9RLQiwi08sB64sffeyXXYGXFBI4E3MDx4rpJDffhlSinyUP/eZ6/tdS2UHf+Djo+Zf3H 4IQ1pafXRKxMNUVLX1rRSI0UgzXTwL0NgFDjWN9kL4/Ocg96tdb/9fYI7cQXhuXUy/zy jpMeKxA9PLn+TifjyXurihr401wFc/UsLj08XL79vPwsP2b6n6KvSkIuuMbzbe1HZdoX bZzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UMCK9MP9WjwNZ9P0ZWCAplyXLZx/3TVtsoohDJUEWts=; b=tWTkuRwiMlqXlj8hzm4v8Egx3HPaxhXEoQreRPiZk9ivfCKarECwyuXQg0l2sZLJns g4Flcf/DJxUdBd7tZrkOARBKQTeK3ykSIRfqk00NZT82dDbzuVUdZAuNsnNqlTEEowls DnWGAH8fKypYOiA4+0LtqWqNF+7gQEA0xbwqz2mokBtXLbxK68M4+jGiBpgtCT+V2XqX bokpYIEkoE+KVq6HsYtiHDWOa6zWgzX/0pnxhfU+L3FkVNVfptp+OyClX8ibKPROnZGy WrmbabRFLmiVHOakvM5T6RBC8xaBlngTbeN1yXdpfMfijCsQUEdhKefLg/i6YWyrBihG bGzQ== X-Gm-Message-State: AHQUAuYv+eU/GrAGFcYockdiM6Al3jXg0kYFZrO0z9ZtqmZK36jEGLA2 iTrDJ0EFG5canEbs5e/LJQr3xcnwAN5nUfgWkoZqCL51 X-Google-Smtp-Source: AHgI3IYOiJehdXYKEMrNWpKhoaJqvrAca/eEgpkqbQ9dj3j/osiW7CssUUMKboI+yrO1wvjyJ74bujKb22Ggp6EzctI= X-Received: by 2002:a9d:6a4:: with SMTP id 33mr25078506otx.347.1549854144344; Sun, 10 Feb 2019 19:02:24 -0800 (PST) MIME-Version: 1.0 From: Adrian Cole Date: Mon, 11 Feb 2019 04:02:12 +0100 Message-ID: Subject: calling our mentors and champion to action (brave-karaf release) To: dev@zipkin.apache.org Content-Type: text/plain; charset="UTF-8" Hi, folks. We just tried to do a release of brave-karaf, but I think we realized that many of us have no experience or no recent experience in ASF releases. Some were giving +1s without doing any verification whatsoever, and others possibly asking for more than required to pass the release. First release was going to be bumpy, so no big deal. However, I think there's some more to it. I think some confusion was caused due to the various incubator mailing list discussions. Some are calling out projects for not doing things right, and some are not clarified on topics about source vs binary etc. The way I perceive these discussions are just that.. discussions. I don't think we have to hold ourselves to standards higher than graduated project (standard of practice). However, I think if this is a valid interpretation, a mentor should step up as sometimes the language in these discussions is distracting (ex blamey phrasing happened in those threads and is strong language for an evolving process especially around github). During our own release, we wandered, possibly into the correct corners, but some topics feel more like guessing what we should do than people knowing they need to. Lacking guidance, personally I looked at a couple projects, jclouds and dubbo, and arbitrarily chose the latter as the docs were polished. https://dubbo.incubator.apache.org/en-us/blog/prepare-an-apache-release.html This doesn't mean they were right, but seems they are right enough. Maybe we can be right enough, too, as re-releasing and meta-discussions are taxing timewise and emotionally. The main thing here is I think we should have not started without a mentor present to help navigate these topics. The short of it is, that as a RM, I'd like to re-start the release vote to clean the slate. I think that involves a "CANCEL" process which I'll look up. However, I'd like a mentor to both be present for questions and also participate in verifying the release and voting. So, if someone can reply with their availability, I'm happy to continue this and learn how to make the next one smooth. Best, -A --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org For additional commands, e-mail: dev-help@zipkin.apache.org