Re: [RESULT] [VOTE] Release commons-parent pom

2006-11-12 Thread Dennis Lundberg
Dennis Lundberg wrote: This VOTE has passed. Result: 7 +1 votes. No other votes. +1: Jochen Wiedmann Dion Gillard Rahul Akolkar Jörg Schaible Niall Pemberton Simon Kitching Henri Yandell I will cut the release this weekend. The pom has been released and has now found its way to the repositor

Re: [RESULT] [VOTE] Release commons-parent pom

2006-11-10 Thread Phil Steitz
belated +1 and THANKS! -Phil On 11/9/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: This VOTE has passed. Result: 7 +1 votes. No other votes. +1: Jochen Wiedmann Dion Gillard Rahul Akolkar Jörg Schaible Niall Pemberton Simon Kitching Henri Yandell I will cut the release this weekend. Thanks

[RESULT] [VOTE] Release commons-parent pom

2006-11-09 Thread Dennis Lundberg
This VOTE has passed. Result: 7 +1 votes. No other votes. +1: Jochen Wiedmann Dion Gillard Rahul Akolkar Jörg Schaible Niall Pemberton Simon Kitching Henri Yandell I will cut the release this weekend. Thanks to everyone who voted. -- Dennis Lundberg Dennis Lundberg wrote: Hello This is a n

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Dennis Lundberg
Henri Yandell wrote: On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues that were raised in the earlier vote has been addressed. So please cast your votes. This vote

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Henri Yandell
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues that were raised in the earlier vote has been addressed. So please cast your votes. This vote will be open for 72 h

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Rahul Akolkar
On 11/7/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Rahul Akolkar wrote: > > a) IMO it needs a ASLv2 header This seems to have been fixed now. > b) Incorrect URL at ${pom.url} (we need to remove "proper/") I've taken care of this. > c) The svn log is confident [1] the antrun bit is need

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Dennis Lundberg
Rahul Akolkar wrote: On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues that were raised in the earlier vote has been addressed. So please cast your votes. Commen

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Simon Kitching
On Tue, 2006-11-07 at 07:43 +0100, Jochen Wiedmann wrote: > On 11/7/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > c) The svn log is confident [1] the antrun bit is needed due to a bug > > in the source plugin, but subsequent conversations not so [2]. What is > > it, IYO? Figure you're as good a

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Simon Kitching
On Mon, 2006-11-06 at 18:47 +0100, Dennis Lundberg wrote: > Hello > > This is a new vote following up on the failed vote [1] that was held > previously. > > As far as I can tell, all the issues that were raised in the earlier > vote has been addressed. So please cast your votes. > > This vote

Re: [VOTE] Release commons-parent pom

2006-11-07 Thread Niall Pemberton
+1 from me (I assume the version number will be updated from "1-SNAPSHOT" when you do the actual release). Niall On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues t

RE: [VOTE] Release commons-parent pom

2006-11-07 Thread Jörg Schaible
+1 Dennis Lundberg wrote on Monday, November 06, 2006 6:48 PM: > Hello > > This is a new vote following up on the failed vote [1] that was held > previously. > > As far as I can tell, all the issues that were raised in the earlier > vote has been addressed. So please cast your votes. > > This

Re: [VOTE] Release commons-parent pom

2006-11-06 Thread Jochen Wiedmann
On 11/7/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: a) IMO it needs a ASLv2 header Ok, done. I also added the LICENSE.txt and NOTICE.txt files to the commons-parent directory. b) Incorrect URL at ${pom.url} (we need to remove "proper/") Can't follow you here. c) The svn log is confide

Re: [VOTE] Release commons-parent pom

2006-11-06 Thread Rahul Akolkar
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues that were raised in the earlier vote has been addressed. So please cast your votes. Comments / questions: a) IM

Re: [VOTE] Release commons-parent pom

2006-11-06 Thread Dion Gillard
Looks good to me. +1 On 11/7/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Sorry, that should of course have been in the original vote mail: http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/pom.xml?revision=471805&view=markup -- Dennis Lundberg Dion Gillard wrote: >

Re: [VOTE] Release commons-parent pom

2006-11-06 Thread Dennis Lundberg
Sorry, that should of course have been in the original vote mail: http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/pom.xml?revision=471805&view=markup -- Dennis Lundberg Dion Gillard wrote: Got a link to the particular artifact we're voting on? On 11/7/06, Dennis Lundb

Re: [VOTE] Release commons-parent pom

2006-11-06 Thread Dion Gillard
Got a link to the particular artifact we're voting on? On 11/7/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues that were raised in the earlier vote has been addressed. So

Re: [VOTE] Release commons-parent pom

2006-11-06 Thread Jochen Wiedmann
+1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Release commons-parent pom

2006-11-06 Thread Dennis Lundberg
Hello This is a new vote following up on the failed vote [1] that was held previously. As far as I can tell, all the issues that were raised in the earlier vote has been addressed. So please cast your votes. This vote will be open for 72 hours and I will tally the votes no earlier than 19: