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 2637C106A2 for ; Fri, 6 Mar 2015 20:10:28 +0000 (UTC) Received: (qmail 4480 invoked by uid 500); 6 Mar 2015 20:10:24 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 4316 invoked by uid 500); 6 Mar 2015 20:10:24 -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 4305 invoked by uid 99); 6 Mar 2015 20:10:24 -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, 06 Mar 2015 20:10:24 +0000 Received: from [192.168.23.9] (host86-152-71-150.range86-152.btcentralplus.com [86.152.71.150]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 441AF1A0490 for ; Fri, 6 Mar 2015 20:10:23 +0000 (UTC) Message-ID: <54FA09A6.1040507@apache.org> Date: Fri, 06 Mar 2015 20:10:14 +0000 From: Mark Thomas User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Commons Developers List Subject: Re: [VOTE] Release BCEL 6.0 based on RC3 References: <1425328677837-4673380.post@n4.nabble.com> <54F4E7DF.4020007@apache.org> <54F4EEDD.4080506@apache.org> <1425670937029-4673474.post@n4.nabble.com> In-Reply-To: <1425670937029-4673474.post@n4.nabble.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit All, This is a community of volunteers. If you want to see something happen, demanding that other people do something is not the way to achieve your aims. At best your demands will have no impact. At worst, they will irritate folks that might have otherwise done the very thing you want to see happen. If you want to see a BCEL release then the best thing you can do is pitch in and help. Jira shows 49 open BCEL issues 4 of which are tagged for 6.0. Take a look at those 4 issues. What needs to be done to resolve them? Is a patch required? Is a review required? Would a test case that demonstrates the issue help (answer "yes!" unless one already exists). A well described bug with a patch and a test case tends to get committed very quickly. If you think some of the BCEL bugs are in this state and being over looked feel free to add a "What else is needed to get this committed?" question on the bug. Of the other 45 issues which ones need to be fixed in 6.0? 6.x? 7.0? I'd me amazed if all of those 45 were valid. Which ones can be closed? If you need versions created in Jira, ask. If you need more karma to assign issues to versions, ask. If you aren't sure what criteria should be used to decide which version to assign issues to, ask. Better still propose some criteria to start the discussion. We don't have suppliers and customers at the ASF. We have a community. Everyone has a part to play. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org