To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-math has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
I personally don't get all the discussion here, because this very question has
imho been discussed a lot in the past (on commons and maven lists).
From what I know the widely agreed output of this discussion has been:
1.) do n PRJ-x-RC-n before cutting a release and vote on them as if they
What do you mean by cutting a release? If this means building the
distribution files, then your points 3.) and 4.) are a contradiction.
Jochen
On Mon, Jun 29, 2009 at 12:14 PM, Mark Strubergstrub...@yahoo.de wrote:
I personally don't get all the discussion here, because this very question
I assume 'cutting a release' as doing a mvn release:stage or something similar.
The release artifacts will only be pushed to the public repos and download
areas etc. after the vote has finally passed.
The way this works basically moves all the effort to the last RC-n voting step.
It is
Hi folks,
some thoughts along the line ...
+) I would like to use the M2 release plugin
+) I don't mind copying the release tag to a RCX SVN tag if the vote fails
+) the commons.rc.version is work-around to distinguish multiple RCs
+) I know that the release process is not perfect but perfect is
Is this project still active? there's a 1.1 release sort of sitting dormant
since ~2007...
