Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A2695183AB for ; Wed, 13 May 2015 05:26:38 +0000 (UTC) Received: (qmail 28726 invoked by uid 500); 13 May 2015 05:26:38 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 28583 invoked by uid 500); 13 May 2015 05:26:38 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 28572 invoked by uid 99); 13 May 2015 05:26:38 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 May 2015 05:26:38 +0000 Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 14BD11A0155 for ; Wed, 13 May 2015 05:26:37 +0000 (UTC) Received: by iecmd7 with SMTP id md7so22266980iec.1 for ; Tue, 12 May 2015 22:26:37 -0700 (PDT) X-Gm-Message-State: ALoCoQnTCwHQ5y1MVD9zbTkG7vuNXYIgq2kCUmku6/enccNT3nOCadx9+4kaWHTwOyisC8DSuzwU MIME-Version: 1.0 X-Received: by 10.107.132.88 with SMTP id g85mr24000978iod.84.1431494797227; Tue, 12 May 2015 22:26:37 -0700 (PDT) Received: by 10.50.85.50 with HTTP; Tue, 12 May 2015 22:26:37 -0700 (PDT) In-Reply-To: <1431464975.17862.3.camel@sludev.com> References: <44lyjbf2sblxcoqtioeb6cst.1431314809556@email.android.com> <1431464975.17862.3.camel@sludev.com> Date: Wed, 13 May 2015 07:26:37 +0200 Message-ID: Subject: Re: [io] Is commons-io dormant? From: Kristian Rosenvold To: Commons Developers List Content-Type: multipart/alternative; boundary=001a113f323ce313ef0515efda2c --001a113f323ce313ef0515efda2c Content-Type: text/plain; charset=UTF-8 2015-05-12 23:09 GMT+02:00 Kervin Pierre : > I'd like to help if possible. What would be involved? > There is an abundance of issues in Jira that should be triaged somewhat before pushing a release. You can fix issues without patches, review existing patches and/or comment on issues. Looking through the open issues it would appear some of them should also be closed or at least moved out of IO. Given that people with committ access *will* be triaging through the current unsolved issues in the next week or two, this is a great time to chip in :) Kristian --001a113f323ce313ef0515efda2c--