Re: [VOTE] Release Apache Portals Pluto 3.0.0

+1 for the re-release mentioned in Scott's email below.

> On Jan 8, 2017, at 11:44 AM, Martin Scott Nicklous =
<[email protected]> wrote:
>=20
> Dear Apache Portals Pluto Team and community,
>=20
> I re-ran the build to correct the problem with the TCK that I =
mentioned in a separate mail, and also to correct the Pluto installer =
plugin naming problem that Neil mentioned. This time, I deployed and ran =
the TCK on the driver. The results (shown below) showed no errors, so I =
think we are good to go.
>=20
> =3D=3D=3D=3D=3D
> Tests run: 6177, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: =
2,169.516 sec - in javax.portlet.tck.driver.TCKSimpleTestDriver
>=20
> Results :
>=20
> Tests run: 6177, Failures: 0, Errors: 0, Skipped: 0
>=20
> [INFO] =
------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] =
------------------------------------------------------------------------
> [INFO] Total time: 37:06 min
> [INFO] Finished at: 2017-01-08T08:48:19+01:00
> [INFO] Final Memory: 81M/159M
> [INFO] =
------------------------------------------------------------------------
> =3D=3D=3D=3D=3D
>=20
> The new release candidate is available from the following maven =
staging repository.:
> =
https://repository.apache.org/content/repositories/orgapacheportals-1014
>=20
> There you will find all source distributions, as well as all Pluto 3.0 =
jar and javadocs artifacts.
>=20
> Additionally, the Portlet API 3.0 (javax.portlet) source, jar and =
javadoc artifacts are packaged here:
> =
https://repository.apache.org/content/repositories/orgapacheportals-1014/j=
avax/portlet/portlet-api/3.0.0
>=20
> We are also providing a binary bundle of the Pluto Container with an =
Tomcat8 ready to use built from the 3.0.0 release candidate:
> =
https://repository.apache.org/service/local/repositories/orgapacheportals-=
1015/content/org/apache/portals/pluto/pluto-bundle/3.0.0/pluto-bundle-3.0.=
0.zip
>=20
> The bundle can be tested by unzipping it, and running start.sh from =
the bin directory, then navigating to http://localhost:8080/pluto, and =
login as pluto/pluto.
>=20
> The release notes are available here:
> =
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D10560&v=
ersion=3D12338869
>=20
> I'm not sure what the proper protocol is - do we all have to vote on =
the release candidate again?=20
>=20
> My vote : +1
>=20
> Mit freundlichen Gr=C3=BC=C3=9Fen, / Kind regards,
> Scott Nicklous
>=20
> WebSphere Portal Standardization Lead & Technology Consultant
> Specification Lead, JSR 362 Portlet Specification 3.0
> IBM Commerce, Digital Experience Development
>=20
> Phone: +49-7031-16-4808 / E-Mail:[email protected] / =
Schoenaicher Str. 220, 71032 Boeblingen, Germany=20
> IBM Deutschland Research & Development GmbH / Vorsitzender des =
Aufsichtsrats: Martina Koederitz / Gesch=C3=A4ftsf=C3=BChrung: Dirk =
Wittkopp=20
> Sitz der Gesellschaft: B=C3=B6blingen / Registergericht: Amtsgericht =
Stuttgart, HRB 243294=20
>=20
> ----- Forwarded by Martin Scott Nicklous/Germany/IBM on 08.01.2017 =
17:17 -----
>=20
> From: DavidSeanTaylor <[email protected]>
> To: [email protected], Portals PMC =
<[email protected]>
> Cc: [email protected]
> Date: 05.01.2017 21:09
> Subject: [VOTE] Release Apache Portals Pluto 3.0.0
>=20
>=20
>=20
>=20
> Dear Apache Portals Pluto Team and community,
>=20
> I've staged a release candidate for the new Apache Portals Pluto 3.0.0 =
release.=20
>=20
> This release candidate includes:
>=20
> * a fully compliant Reference Implementation of the new Portlet 3.0 =
Specification per JCR-362
> https://www.jcp.org/en/jsr/detail?id=3D362
> * a completed TCK (Test Compatibility Kit) for Portlet Spec 3.0
>=20
> The Portlet API 3.0 specification has been approved by the JCP (JSR =
362 Public Review Ballot), see:
>=20
> https://www.jcp.org/en/jsr/results?id=3D5896
>=20
>=20
> Please review the release candidate for this project which is =
available from the following maven staging repository:
>=20
> =
https://repository.apache.org/content/repositories/orgapacheportals-1012/
> There you will find all source distributions, as well as all Pluto 3.0 =
jar and javadocs artifacts.
>=20
> Additionally, the Portlet API 3.0 (javax.portlet) source, jar and =
javadoc artifacts are packaged here:
>=20
> =
https://repository.apache.org/content/repositories/orgapacheportals-1012/j=
avax/portlet/portlet-api/3.0.0/
>=20
> We are also providing a binary bundle of the Pluto Container with an =
Tomcat8 ready to use built from the 3.0.0 release candidate:
> =
https://repository.apache.org/content/repositories/orgapacheportals-1013/o=
rg/apache/portals/pluto/pluto-bundle/3.0.0/
>=20
> The bundle can be tested by unzipping it, and running start.sh from =
the bin directory, then navigating to http://localhost:8080/pluto, and =
login as pluto/pluto.
>=20
> The release notes are available here:
>=20
> =
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D10560&v=
ersion=3D12338869
>=20
>=20
> The KEYS file to verify the release artifacts signature can be found =
here:
>=20
> https://dist.apache.org/repos/dist/release/portals/pluto/KEYS
>=20
> Please review the release candidates and vote on releasing Apache =
Portals Pluto 3.0.0
>=20
> This vote is open for the next 72 hours.
>=20
> Please cast your vote:
>=20
> [ ] +1 for Release
> [ ] 0 for Don't care
> [ ] -1 Don't release (do provide a reason then)
>=20
> Regards,
>=20
> David Sean Taylor
>=20
>=20