-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
By my count, we have the following results:
3 +1s from Apache WS PM members (http://ws.apache.org/#Members)
6 non-binding +1s
No other votes were cast.
I am therefore pleased to announce that the vote has passed!
We did, however, get some requests from Tom Jordahl on the ws-general
list:
1. Include the ChangeLog.txt in the distribution (my fault -- it's
in the svn repo, but not the dist)
2. Indicate that the Jiras fixed were only fixed in the 1.5.4 release
3. Change the front page to indicate the release version and date
I'm not exactly sure how to proceed with this, though I can present
some alternatives:
A. Manually modify the distribution and site before deployment
B. Modify the branch/tag to reflect these changes
C. Modify the mainline only to reflect these changes
D. Respin a set of bits/Jars
I'm pretty firmly against D, because properly speaking, we would have
to re-vote on the release (ship the bits you test). Strictly
speaking, we would be violating that rule by tampering with the
distribution ZIP, but we would not be changing any of the built bits,
so in that sense, I think A is okay, at least marginally.
The problem comes with build reproducibility; if we ever wanted to
reproduce the bits as released (site and dist), we'd rightfully need
to make the changes on the branch/tag.
The real question is, what is the liklihood of that? I'd say it's
pretty UNlikely, and is worth the risk to just make manual changes to
the site and distribution ZIP, and then just record the changes on the
mainline, for future reference.
So I guess I'm inclined towards a combination of A and C, with perhaps
a note in the README in the tag indicating what additional manual
steps were taken for the dist and site changes.
Thanks!
- -Fred
On May 27, 2008, at 11:38 AM, Fred Dushin wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To the Apache Web Services Community,
This is a second call for votes for the wss4j-1.5.4 release. This
release has the same set of fixes as the version previously voted
on, and, in addition, contains a fix for WSS-119.
The distribution can be found at the following URL:
http://people.apache.org/~fadushin/stage/wss4j/1.5.4/dist/
You can also point maven at the following URL to pull down the 1.5.4
release POM, source, and class JARs:
http://people.apache.org/~fadushin/stage/wss4j/1.5.4/maven/
Additionally, the generated version of the web site can be found at
http://people.apache.org/~fadushin/stage/wss4j/1.5.4/site
Note that for the record, the previously voted-on release can be
found at
http://people.apache.org/~fadushin/stage/wss4j/1.5.4-RETRACTED
This vote will stay open for at least 72 hours.
Thank you for all the effort made towards this release, and for your
patience with this re-spin.
Here is my (non-binding and advisory) +1
- -Fred
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFIPCruKSQw0yA4Kl8RAl7uAKCb46XkbyiQQ1CgbpNb4DsaT0aHuwCeIYie
x7WGLd1CYYaARyNpLZON6yw=
=/W4l
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFIQET5KSQw0yA4Kl8RAtpMAJ9SAq2Un7sRxGfhnAb4VeyzgPPzVwCfTGbC
gPs6jz3QrvZcKFQE1iCeKvs=
=6XqB
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
