+1 6 votes for and none against. We’ll finalize the release now. Thanks for voting on the Pluto 3.0 Release!
[6] +1 for Release [0] 0 for Don't care [0] -1 Don't release (do provide a reason then) > On Jan 10, 2017, at 1:29 PM, Neil Griffin <[email protected]> > wrote: > > +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: >> >> Dear Apache Portals Pluto Team and community, >> >> 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. >> >> ===== >> Tests run: 6177, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2,169.516 >> sec - in javax.portlet.tck.driver.TCKSimpleTestDriver >> >> Results : >> >> Tests run: 6177, Failures: 0, Errors: 0, Skipped: 0 >> >> [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] >> ------------------------------------------------------------------------ >> ===== >> >> The new release candidate is available from the following maven staging >> repository.: >> https://repository.apache.org/content/repositories/orgapacheportals-1014 >> >> There you will find all source distributions, as well as all Pluto 3.0 jar >> and javadocs artifacts. >> >> Additionally, the Portlet API 3.0 (javax.portlet) source, jar and javadoc >> artifacts are packaged here: >> https://repository.apache.org/content/repositories/orgapacheportals-1014/javax/portlet/portlet-api/3.0.0 >> >> 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 >> >> 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. >> >> The release notes are available here: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10560&version=12338869 >> >> I'm not sure what the proper protocol is - do we all have to vote on the >> release candidate again? >> >> My vote : +1 >> >> Mit freundlichen Grüßen, / Kind regards, >> Scott Nicklous >> >> WebSphere Portal Standardization Lead & Technology Consultant >> Specification Lead, JSR 362 Portlet Specification 3.0 >> IBM Commerce, Digital Experience Development >> >> Phone: +49-7031-16-4808 / E-Mail:[email protected] / Schoenaicher >> Str. 220, 71032 Boeblingen, Germany >> IBM Deutschland Research & Development GmbH / Vorsitzender des >> Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp >> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, >> HRB 243294 >> >> ----- Forwarded by Martin Scott Nicklous/Germany/IBM on 08.01.2017 17:17 >> ----- >> >> 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 >> >> >> >> >> Dear Apache Portals Pluto Team and community, >> >> I've staged a release candidate for the new Apache Portals Pluto 3.0.0 >> release. >> >> This release candidate includes: >> >> * a fully compliant Reference Implementation of the new Portlet 3.0 >> Specification per JCR-362 >> https://www.jcp.org/en/jsr/detail?id=362 >> * a completed TCK (Test Compatibility Kit) for Portlet Spec 3.0 >> >> The Portlet API 3.0 specification has been approved by the JCP (JSR 362 >> Public Review Ballot), see: >> >> https://www.jcp.org/en/jsr/results?id=5896 >> >> >> Please review the release candidate for this project which is available from >> the following maven staging repository: >> >> 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. >> >> Additionally, the Portlet API 3.0 (javax.portlet) source, jar and javadoc >> artifacts are packaged here: >> >> https://repository.apache.org/content/repositories/orgapacheportals-1012/javax/portlet/portlet-api/3.0.0/ >> >> 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/org/apache/portals/pluto/pluto-bundle/3.0.0/ >> >> 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. >> >> The release notes are available here: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10560&version=12338869 >> >> >> The KEYS file to verify the release artifacts signature can be found here: >> >> https://dist.apache.org/repos/dist/release/portals/pluto/KEYS >> >> Please review the release candidates and vote on releasing Apache Portals >> Pluto 3.0.0 >> >> This vote is open for the next 72 hours. >> >> Please cast your vote: >> >> [ ] +1 for Release >> [ ] 0 for Don't care >> [ ] -1 Don't release (do provide a reason then) >> >> Regards, >> >> David Sean Taylor >> >> >
