Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of thomas.neidhart@gmail.com
 designates 74.125.82.181 as permitted sender)
Message-ID: <513B47D9.2080204@gmail.com>
Date: Sat, 09 Mar 2013 15:31:53 +0100
From: Thomas Neidhart <thomas.neidhart@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [VOTE] release Apache Commons-FileUpload 1.3 based on RC1
References: 
 <CAAqLGLPFGM6q552WZoB6++-6q1WpuQH+7UiUREZ_s1LMP7FHNQ@mail.gmail.com>
 <513B3E58.4020008@gmail.com>
 <CAAqLGLM4SVVKCGX18Qp=CFA4DZDyTBvcLG0URLx5zmLyp8sAnw@mail.gmail.com>
In-Reply-To: 
 <CAAqLGLM4SVVKCGX18Qp=CFA4DZDyTBvcLG0URLx5zmLyp8sAnw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 03/09/2013 03:23 PM, Simone Tripodi wrote:
> Hi Thomas,
> 
> The user proposed a solution - without a patch - that, in his opinion,
> should work.
> We do not have a testcase which proves the reported issue, which would
> affect all past FileUpload releases.
> 
> So, my question (to everybody) is: could the resolution of that issue
> postponed to 1.3.1 or it is a blocker for 1.3?
> TIA,

I do not think its the responsibility of the users that our provided
software is bug-free. If they do submit patches, great, if not, somebody
has to step in.

The more interesting question for me is if there is any specific reason
why this component has to be rushed out? Any important bugfix that
somebody needs? I ask, because I see more bugs which seem to be easy to
fix. Do you need help for that?

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org