I guess JCR-362 means JSR-362, as JCR (Java Content Repository) also
relates to Portlets but those are different JSRs.

Regards,
Werner



On Fri, May 11, 2018 at 9:06 PM, Neil Griffin <neil.grif...@portletfaces.org
> wrote:

> Dear Apache Portals Pluto Team and community,
>
> I've staged a release 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 spread
> across the following THREE maven staging repositories:
>
> 1) portlet-api and pluto-portal components and dependencies:
> https://repository.apache.org/content/repositories/orgapacheportals-1018
>
> 2) pluto+tomcat bundle:
> https://repository.apache.org/content/repositories/orgapacheportals-1019
>
>     (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.)
>
> 3) maven archetypes:
> https://repository.apache.org/content/repositories/orgapacheportals-1020
>
> The Release Notes are available here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=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
>
> Seeing as how I am sending this on a Friday, 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
>

Reply via email to