Hi all guys,
the Digester3 RC1 can be considered failed due to missing release
requirements that Luc reported.
Thanks everybody who put his effort on reviewing, and be ready for the RC2!!!
Have a nice day, all the best!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri
Le 01/07/2011 15:08, Simone Tripodi a écrit :
Salut Luc,
Hi Simone,
can we close this vote thread in order I can fix the open issues or we
have to wait this evening?
I guess you can cancel it and prepare a new one. I'm pretty sure people
will wait for the next RC to check it.
best regard
Salut Luc,
can we close this vote thread in order I can fix the open issues or we
have to wait this evening?
Many thanks in advance, have a nice day!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Jul 1, 2011 at 3:06 PM, Luc Maisonobe wrote:
> Le 01/07/2011 15:02,
Le 01/07/2011 15:02, Simone Tripodi a écrit :
Salut Luc!
-1
The gpg signature seems to have been done with key 41A0D191 which is not
your Apache signing key. The Apache signature key present in the KEYS file
is either 19FEA27D or C002CC79.
my bad :/
There are also a few other minor issue
Salut Luc!
>
> -1
>
> The gpg signature seems to have been done with key 41A0D191 which is not
> your Apache signing key. The Apache signature key present in the KEYS file
> is either 19FEA27D or C002CC79.
>
my bad :/
> There are also a few other minor issues:
>
> - a few checkstyle errors, mai
Le 28/06/2011 21:41, Simone Tripodi a écrit :
Hi all guys!
I just deployed the Maven artifacts on Nexus (details below), so
please cast your votes! :)
Vote will be open for next 72 hours and will be closed on July 1st, at 7:40pm.
Many thanks in advance!!!
Simo
Release Notes:
http://people.apach
Hi Simone,
Simone Tripodi wrote:
> Hi all guys!
> I just deployed the Maven artifacts on Nexus (details below), so
> please cast your votes! :)
> Vote will be open for next 72 hours and will be closed on July 1st, at
> 7:40pm. Many thanks in advance!!!
> Simo
>
> Release Notes:
>
> http://peopl
Hi all guys and thank for your support!
Apologize for the async due to to our different timezones :(
So, IIUC:
- renaming the tag should be enough, I mean:
svn mv
https://svn.apache.org/repos/asf/commons/proper/digester/tags/commons-digester3-3.0/
https://svn.apache.org/repos/asf/commons/pro
Another email thread about the mechanics of releasing :(
As a recent RM who went through my own pains, I send Simone my best wishes.
I do not know how to fix this though.
How does this work in other communities?
Gary
On Wed, Jun 29, 2011 at 1:52 PM, Phil Steitz wrote:
> On 6/29/11 10:44 AM,
On 6/29/11 10:44 AM, Matt Benson wrote:
> On Wed, Jun 29, 2011 at 11:49 AM, Phil Steitz wrote:
>> On 6/29/11 8:58 AM, Simone Tripodi wrote:
>>> Hi all guys,
>>> I just realized that the tag[1] dir name is in the wrong pattern - I
>>> overlooked the fact that the release:plugin tagged with the defa
On Wed, Jun 29, 2011 at 11:49 AM, Phil Steitz wrote:
> On 6/29/11 8:58 AM, Simone Tripodi wrote:
>> Hi all guys,
>> I just realized that the tag[1] dir name is in the wrong pattern - I
>> overlooked the fact that the release:plugin tagged with the default
>> one :(
>> Now the question is: is it fi
On 6/29/11 8:58 AM, Simone Tripodi wrote:
> Hi all guys,
> I just realized that the tag[1] dir name is in the wrong pattern - I
> overlooked the fact that the release:plugin tagged with the default
> one :(
> Now the question is: is it fine just moving it with a 'svn move' or
> the RC has to be reb
Hi all guys,
I just realized that the tag[1] dir name is in the wrong pattern - I
overlooked the fact that the release:plugin tagged with the default
one :(
Now the question is: is it fine just moving it with a 'svn move' or
the RC has to be rebuilt from scratch?
Many thanks in advance, have a nice
Hi Dave,
very nice to meet you and thanks for reporting!
That should be non blocking, once the 3.0 release passed, the
3.1-SNAPSHOT site will be re-deployed and will override wrong
link/deprecated and already fixed references!
Have a nice day!
Simo
http://people.apache.org/~simonetripodi/
http://w
Perhaps i am confused but it appears the source code links on the web site
(http://commons.apache.org/digester/source-repository.html) are
wrong,http://svn.apache.org/viewvc/commons/sandbox/digester3/trunk
svn checkout http://svn.apache.org/repos/asf/commons/sandbox/digester3/trunk
commons-dig
Hi all guys!
I just deployed the Maven artifacts on Nexus (details below), so
please cast your votes! :)
Vote will be open for next 72 hours and will be closed on July 1st, at 7:40pm.
Many thanks in advance!!!
Simo
Release Notes:
http://people.apache.org/builds/commons/digester/3.0/RC1/RELEASE-NO
Hi Seb!
I'm going to checkout the tag and deploy artifacts, that should work!
Thanks,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Jun 28, 2011 at 8:12 PM, sebb wrote:
> On 28 June 2011 09:52, Simone Tripodi wrote:
>> Hi all guys!!!
>> and sorry for the delay -
On 28 June 2011 09:52, Simone Tripodi wrote:
> Hi all guys!!!
> and sorry for the delay - I have no idea why maven artifacts haven't
> been deployed on Nexus; I tried do deploy a SNAPSHOT version and they
> were successfully/automatically deployed on Nexus; once executed the
> release plugin, they
Hi all guys!!!
and sorry for the delay - I have no idea why maven artifacts haven't
been deployed on Nexus; I tried do deploy a SNAPSHOT version and they
were successfully/automatically deployed on Nexus; once executed the
release plugin, they were deployed via scp...
Any hint/suggestion?
Many than
On 6/27/11 3:11 PM, James Carman wrote:
> Should we all be performing releases the same way? We are one project with
> multiple components. We should have a standardized release process.
We have common release *requirements* but RMs are free to use the
tools that they wish to produce and publish
On 6/27/11 3:13 PM, sebb wrote:
> On 27 June 2011 22:51, Phil Steitz wrote:
>> On 6/27/11 2:39 PM, sebb wrote:
>>> On 27 June 2011 20:44, Simone Tripodi wrote:
Hi all guys,
I recently come back focusing on Digester3, fixed some old Issue/added
new minor features and IMHO it is now
On 27 June 2011 22:51, Phil Steitz wrote:
> On 6/27/11 2:39 PM, sebb wrote:
>> On 27 June 2011 20:44, Simone Tripodi wrote:
>>> Hi all guys,
>>> I recently come back focusing on Digester3, fixed some old Issue/added
>>> new minor features and IMHO it is now in a good state to be released.
>>> Tha
Should we all be performing releases the same way? We are one project with
multiple components. We should have a standardized release process.
Sent from tablet device. Please excuse typos and brevity.
On Jun 27, 2011 5:53 PM, "Phil Steitz" wrote:
> On 6/27/11 2:39 PM, sebb wrote:
>> On 27 June
On 6/27/11 2:39 PM, sebb wrote:
> On 27 June 2011 20:44, Simone Tripodi wrote:
>> Hi all guys,
>> I recently come back focusing on Digester3, fixed some old Issue/added
>> new minor features and IMHO it is now in a good state to be released.
>> That's why I'm calling that vote :)
>> So please cast
On 27 June 2011 20:44, Simone Tripodi wrote:
> Hi all guys,
> I recently come back focusing on Digester3, fixed some old Issue/added
> new minor features and IMHO it is now in a good state to be released.
> That's why I'm calling that vote :)
> So please cast your votes!!! Many thanks in advance t
Hi again,
forgot to mention the Release Notes:
http://people.apache.org/builds/commons/digester/3.0/RC1/RELEASE-NOTES.txt
Thanks!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Jun 27, 2011 at 9:44 PM, Simone Tripodi
wrote:
> Hi all guys,
> I recently come back
Hi all guys,
I recently come back focusing on Digester3, fixed some old Issue/added
new minor features and IMHO it is now in a good state to be released.
That's why I'm calling that vote :)
So please cast your votes!!! Many thanks in advance to everybody will
take part to the review, very appreciat
27 matches
Mail list logo
