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 B7690200B43 for ; Wed, 8 Jun 2016 01:09:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B4B79160A4F; Tue, 7 Jun 2016 23:09:22 +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 07F99160A36 for ; Wed, 8 Jun 2016 01:09:21 +0200 (CEST) Received: (qmail 80095 invoked by uid 500); 7 Jun 2016 23:09:21 -0000 Mailing-List: contact dev-help@fluo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.incubator.apache.org Delivered-To: mailing list dev@fluo.incubator.apache.org Received: (qmail 80019 invoked by uid 99); 7 Jun 2016 23:09:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2016 23:09:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 788A2C0773 for ; Tue, 7 Jun 2016 23:09:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=deenlo-com.20150623.gappssmtp.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id FMWUwo2Yz93T for ; Tue, 7 Jun 2016 23:09:18 +0000 (UTC) Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 77F735F574 for ; Tue, 7 Jun 2016 23:09:17 +0000 (UTC) Received: by mail-oi0-f48.google.com with SMTP id k23so301558418oih.0 for ; Tue, 07 Jun 2016 16:09:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=deenlo-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=WTnyyV3MSR0tYDkF49CcndEiZgpMXT9fqPe4edSfcM0=; b=bMUM7gJXYmTrc2GBoo0DjGv51QAla3W3UJspKdGrG9P3AGCayrJmz6DxHzs40yyJPJ j3zppC5FlDab2+NwSHZDCvuRX3ODy17zL/lgudW73s10fhsuZiSBE8OLVrIFcbV3MAhc nZgv7ZGL6fzjdm/h5ZjDb46XKu4S2FztWmVYM3SUbixHJH+y5//WXAhv/oqjR44U4bqE JIV3FwGbrRNcl5diTC1ylulQe6wz3LRsecDCcYCEo4h3sqV31xKyyUFSUX0IYl+vd/9u Mjkvvkow7RCQ6AKxaSkM1P9kk3a7ceUsBSJnFwB3s61/PeC7+ZQs6CnzU7UvspRpe+Ad ssAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=WTnyyV3MSR0tYDkF49CcndEiZgpMXT9fqPe4edSfcM0=; b=AU1IA4ZEw0qFgyjEyIxMkpXeya7SBI5dv8okR3qKl8/Os+w228iAxAi7lL8hLALtg6 9yCKzZO+AcGWRsCEqURhSHetyI5iwYfovP2vLwiYRMFi/PJ68Bcy5pQXejziGCPXyQtP 3sARYuCpJSms+mEH2bFuRHECUClpYrrpOH8bDTK3n5DXzZxXXIoSfPbwEsjlvxHj89Jx WEz/a+h80EJlUgkTHD9GUgiknqqF2QM1sustAf+6K3NN0Elj2Rf3JRrDJ8mw3G75KElt 6KR7YUQ+ms5hK6TSvOC5pLRCOz/AM16fiNeh+maRXxV+azmWfxdm3uxDZSd1sxTNsQsf SrIQ== X-Gm-Message-State: ALyK8tLrLSyy2t7ayqLOMwkLgBC2/FUibUtqkWdxSVIcDh14YiE9/79kHb/xvisZsuHig+dlYuwvNcKEUw2CMA== MIME-Version: 1.0 X-Received: by 10.157.38.141 with SMTP id l13mr1067628otb.193.1465340956202; Tue, 07 Jun 2016 16:09:16 -0700 (PDT) Received: by 10.202.216.6 with HTTP; Tue, 7 Jun 2016 16:09:16 -0700 (PDT) In-Reply-To: References: <57573CF8.2000802@gmail.com> Date: Tue, 7 Jun 2016 19:09:16 -0400 Message-ID: Subject: Re: Releasing Fluo incubating 1.0.0 From: Keith Turner To: dev@fluo.incubator.apache.org Content-Type: multipart/alternative; boundary=001a113d0efa2b75410534b8473a archived-at: Tue, 07 Jun 2016 23:09:22 -0000 --001a113d0efa2b75410534b8473a Content-Type: text/plain; charset=UTF-8 I am not sure why infra does not answer our questions on the issue. On Tue, Jun 7, 2016 at 6:31 PM, Christopher wrote: > I haven't had time to follow up yet. Sorry. And I might be busy this week > to do it. If somebody else wants to facilitate the conversation, I can > grant the infra user access. (Keith or Mike could do it, too) > > On Tue, Jun 7, 2016 at 5:30 PM Josh Elser wrote: > > > Any progress? > > > > Christopher wrote: > > > I commented in HipChat #asfinfra yesterday asking for help with our git > > > setup: > > > > > > [9:36 PM] Christopher Tubbs (ctubbsii): Is anybody available to assist > > with > > > INFRA-11901? Basically, we just need to transfer the GitHub repos over > to > > > ASF land so the GitHub issues and existing code history go with it. > > > Essentially, same thing Pony did. I can grant ownership temporarily to > > our > > > existing GitHub org so an INFRA member can do the transfer/rename/etc. > > > [9:37 PM] Christopher Tubbs (ctubbsii): If not, no big deal. I can > check > > > back tomorrow (earlier in the day). > > > > > > , but nobody was around that late. I meant to try again today, but got > > > distracted with other stuffs. I can try again on Monday... or maybe > over > > > the weekend (not likely over the weekend, though). > > > > > > On Fri, Jun 3, 2016 at 3:43 PM Keith Turner wrote: > > > > > >> IMO Fluo is ready for a 1.0.0 release. It really nice that we can > now > > do > > >> this with Apache package names and Maven coordinates. I am trying to > > >> brainstorm what needs to be done before releasing 1.0.0. I feel like > we > > >> are in limbo waiting on INFRA, but I would like to get the ball > rolling > > on > > >> working towards putting a 1.0.0 release up for a vote. Here is my > quick > > >> list of things to do, what else needs to be added? > > >> > > >> * Rename packages and make any needed documentation updates > > >> * Run Fluo stress test on EC2 > > >> * Legal stuff?? > > >> * Triage any issues that we want fixed before 1.0.0 > > >> * Having an Apache web site for Fluo is a prerequisite > > >> * Make pom updates for doing a release. > > >> > > > > > > --001a113d0efa2b75410534b8473a--