On 2 June 2011 20:22, sebb wrote:
> This is a vote to release Apache Commons NET 3.0.1 based on RC3.
>
> Very little has changed since 3.0; the release is being made to
> correct a regression in the FTPClient storeFile method.
Here's my vote:
> [X] +1 release it
> [ ] +0 go ahead I don't care
>
sebb wrote:
> This is a vote to release Apache Commons NET 3.0.1 based on RC3.
>
> Very little has changed since 3.0; the release is being made to
> correct a regression in the FTPClient storeFile method.
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
On 2011-06-04 19:33, Henri Yandell wrote:
> On Fri, Jun 3, 2011 at 7:43 PM, Phil Steitz wrote:
>> On 6/3/11 7:27 PM, Henri Yandell wrote:
>>> On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi
>>> wrote:
> I think that is also best practice - resolve when fixed in SVN,
> close when fix versi
On 4 June 2011 18:33, Henri Yandell wrote:
> On Fri, Jun 3, 2011 at 7:43 PM, Phil Steitz wrote:
>> On 6/3/11 7:27 PM, Henri Yandell wrote:
>>> On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi
>>> wrote:
> I think that is also best practice - resolve when fixed in SVN,
> close when fix ver
On Fri, Jun 3, 2011 at 7:43 PM, Phil Steitz wrote:
> On 6/3/11 7:27 PM, Henri Yandell wrote:
>> On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi
>> wrote:
I think that is also best practice - resolve when fixed in SVN,
close when fix version is released.
>>> I couldn't agree more!!!
Le 04/06/2011 04:43, Phil Steitz a écrit :
On 6/3/11 7:27 PM, Henri Yandell wrote:
On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi wrote:
I think that is also best practice - resolve when fixed in SVN,
close when fix version is released.
I couldn't agree more!!! +1!
I just close directly. Th
+1
Contents look good.
Sigs / hashes are good.
Checked source build with
Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode)
Nice work!
Phil
On 6/2/11 12:22 PM, sebb wrote:
> This is a vote to release Apache Commons
On 3 June 2011 21:54, Phil Steitz wrote:
> On 6/3/11 1:15 PM, sebb wrote:
>> On 3 June 2011 20:48, Gary Gregory wrote:
>>> On Fri, Jun 3, 2011 at 2:53 PM, sebb wrote:
>>>
On 3 June 2011 19:21, Gary Gregory wrote:
> +1.
>
> I would like to see the JIRA report be only for this re
On 6/3/11 7:27 PM, Henri Yandell wrote:
> On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi
> wrote:
>>> I think that is also best practice - resolve when fixed in SVN,
>>> close when fix version is released.
>>>
>> I couldn't agree more!!! +1!
> I just close directly. The resolve then close is a wo
On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi wrote:
>>
>> I think that is also best practice - resolve when fixed in SVN,
>> close when fix version is released.
>>
>
> I couldn't agree more!!! +1!
I just close directly. The resolve then close is a workflow waiting
for a reason :)
Hen
>
> I think that is also best practice - resolve when fixed in SVN,
> close when fix version is released.
>
I couldn't agree more!!! +1!
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: d
On 6/3/11 1:15 PM, sebb wrote:
> On 3 June 2011 20:48, Gary Gregory wrote:
>> On Fri, Jun 3, 2011 at 2:53 PM, sebb wrote:
>>
>>> On 3 June 2011 19:21, Gary Gregory wrote:
+1.
I would like to see the JIRA report be only for this release instead of
>>> the
whole pile.
>>> That'
+1
I agree, due to our policy to manage Issues, the jira-report is not very useful
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Jun 3, 2011 at 10:15 PM, sebb wrote:
> On 3 June 2011 20:48, Gary Gregory wrote:
>> On Fri, Jun 3, 2011 at 2:53 PM, sebb wrote:
>>
>
On 3 June 2011 20:48, Gary Gregory wrote:
> On Fri, Jun 3, 2011 at 2:53 PM, sebb wrote:
>
>> On 3 June 2011 19:21, Gary Gregory wrote:
>> > +1.
>> >
>> > I would like to see the JIRA report be only for this release instead of
>> the
>> > whole pile.
>>
>> That's the default setting for the plugi
On Fri, Jun 3, 2011 at 2:53 PM, sebb wrote:
> On 3 June 2011 19:21, Gary Gregory wrote:
> > +1.
> >
> > I would like to see the JIRA report be only for this release instead of
> the
> > whole pile.
>
> That's the default setting for the plugin.
>
Not a very useful default then :(
Running vs. t
On 3 June 2011 19:21, Gary Gregory wrote:
> +1.
>
> I would like to see the JIRA report be only for this release instead of the
> whole pile.
That's the default setting for the plugin.
I'd not noticed the report before.
Not sure it's all that useful - hardly any other components use it:
./sandb
+1.
I would like to see the JIRA report be only for this release instead of the
whole pile.
Shouldn't the Clirr report be vs. 3.0 instead of 2.2?
My set up:
Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: C:\Java\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun
+1
very nice release, everything looks really good, congrats!!!
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Thu, Jun 2, 2011 at 9:22 PM, sebb wrote:
> This is a vote to release Apache Commons NET 3.0.1 based on RC3.
>
> Very little has changed since 3.0; the release is b
This is a vote to release Apache Commons NET 3.0.1 based on RC3.
Very little has changed since 3.0; the release is being made to
correct a regression in the FTPClient storeFile method.
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because...
tag: http://svn.apache.o
19 matches
Mail list logo
