David Jencks wrote:
-1
I think the scm info is wrong. I'm also always reluctant to vote on
something that is not the final artifact in its final location: in this
case it would be a pom under portals-pom/tags with version 1.0.
I think Vivek did propose the vote on the current trunk version with the intend to have its logical content validated/verified, and not so
much from the formal release procedure POV,
But besides that, and I agree its better procedure to first create a release and then vote upon that, the scm info was not correct anyway as
it didn't point to the trunk either.
I just see you've already updated this, thanks!
If you are using the release plugin (as implied by the use of the apache
pom version 5) and the apache nexus for releases I'd expect the artifact
for voting would be in a staging repo in nexus.
I'm not aware exactly how that works either, other than having seem some
messages fly by recently for a Nexus Repo @ASF.
Like David Taylor, I'd appreciate it if you know of some pointers to current
documentation how to release using Nexus nowadays?
Also the indenting looks inconsistent in firefox -- mostly tabs but I
think a few spaces. Not enough for a -1 but if the scm info needs to be
fixed fixing the indent should be easy.
If I'm wrong about the scm info I'll happily withdraw the -1.
thanks
david jencks
Thanks for monitoring David, that really is appreciated as is your help in
fixing the poms.
Regards,
Ate
On Mar 17, 2009, at 9:14 AM, Vivek Kumar wrote:
Hi,
I have now prepared a new generic portals parent POM for use by all
subproject within
Portals. I'd like to make a release of this parent POM so that we can
start referring to a non-SNAPSHOT version.
The release candidate (essentially just the pom.xml file) is available
for review in
http://svn.apache.org/viewvc/portals/portals-pom/trunk/pom.xml?view=markup
Please vote on releasing this version 1.0 of the Portals-pom
POM. The vote is open for the next 72 hours.
[ ] +1 for Release
[ ] -1 Don't release, reason
Here's my +1.
Vivek Kumar
