Sorry, David for the mixed message.
The binary release that you cut produced an 'About Pluto' portlet that
indicated that the Pluto version was 1.1.0-SNAPSHOT. I added changes to
the beta2 tag where About Pluto now reports the Pluto version of
1.1.0-beta2. I also updated files in the beta2 tagged directory to make
the version test in the testsuite to work correctly with a 1.1.0-beta2
version.
Therefore, I give a -1 to releasing the original binary cut that you
did, and a +1 to a version based on what is now in the SVN beta2 tagged
directory
(http://svn.apache.org/viewvc/portals/pluto/tags/release-1.1.0-beta2/).
It's a small change, but very significant to allow a user to tell what
version of Pluto he/she is using at the time via the About Pluto
portlet.This information is very valuable in a Jira or
pluto-user/pluto-dev post of a problem with Pluto.
/Craig
P.S. I put binary cuts of the new version in
http://people.apache.org/~cdoremus/pluto/pluto-1.1-dist/beta2/
hmmm. . .so I'm not sure what your suggesting. . .
a +1 means roll the release the way it is, but your email suggests
that we recut it. Can you explain??? Either way, the tag should
match the release, not a modified version of the release.
David
[EMAIL PROTECTED] wrote:
+1
I found a minor issue with the proper version not displaying in the
'About
Pluto' portlet and added fixes to the 1.1.0-beta2 tagged branch in
Subversion.
/Craig
Original Message:
-----------------
From: David H. DeWolf [EMAIL PROTECTED]
Date: Sat, 23 Sep 2006 20:30:48 -0400
To: [email protected]
Subject: [VOTE] 1.1.0-beta2
The test builds for 1.1.0-beta2 have been out for almost a week.
I've heard of no issues. Please vote as to whether or not we should
release these binaries.
Thanks,
David
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
