@Scott: I just added them to SVN and also updated the release instructions: https://github.com/apache/portals-pluto/commit/e99b97a2b9b3a5b58f872a2188af7d01f4167520
On 6/18/18 4:13 AM, Martin Scott Nicklous wrote:
Hi Neil, thank you very much for this!! Not meaning to nit-pick, but does the pluto-bundle-3.0.1.zip file require signature files? They don't seem to be present in the /dist/dev/portals/pluto/ directory ... 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 Inactive hide details for Neil Griffin ---16.06.2018 03:07:34---Dear Apache Portals Pluto Team and community, It took me a few Neil Griffin ---16.06.2018 03:07:34---Dear Apache Portals Pluto Team and community, It took me a few weeks to find room in my schedule, bu From: Neil Griffin <[email protected]> To: [email protected] Cc: [email protected] Date: 16.06.2018 03:07 Subject: [VOTE] Release Apache Portals Pluto 3.0.1 (Second Attempt) ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Dear Apache Portals Pluto Team and community, It took me a few weeks to find room in my schedule, but thanks to Woonsan's helpful advice I've staged another candidate for the new Apache Portals Pluto 3.0.1 release. This release candidate includes: * Fully compliant Reference Implementation of the new Portlet 3.0 Specification per JCR-362 https://www.jcp.org/en/jsr/detail?id=362 * Fully completed (and corrected) TCK (Test Compatibility Kit) for Portlet Spec 3.0 * Updated portlet-api with associated Javadoc improvements * General bugfixes * Updated archetypes Please review the release candidate for this project which is found in the following maven staging repository: https://repository.apache.org/content/repositories/orgapacheportals-1022/ As Woonsan asked, the source and other artifacts have been made available at the /dist/dev directory: https://dist.apache.org/repos/dist/dev/portals/pluto/ (These files will be promoted to /dist/release if the vote passes) The Release Notes are available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10560&version=12338908 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.1 REMINDER: According to the following policy: http://www.apache.org/legal/release-policy.html#release-approval "Before casting +1 binding votes, individuals are REQUIRED to download all signed source code packages onto their own hardware, verify that they meet all requirements of ASF policy on releases as described below, validate all cryptographic signatures, compile as provided, and test the result on their own platform." Seeing as how I am sending this on a Friday again, the normal vote of 72 hours seems unreasonable. Therefore I would like to extend the vote to 96 hours. Please cast your vote: [ ] +1 for Release [ ] 0 for Don't care [ ] -1 Don't release (do provide a reason then) Best Regards to all, Neil
