+1

On Tue, Dec 12, 2023 at 7:33 PM Vernon Singleton <vsingle...@gmail.com>
wrote:

> Looks good.
> +1
>
> On Tue, Dec 12, 2023 at 7:00 PM Neil Griffin <portletfa...@gmail.com>
> wrote:
> >
> > Dear Apache Portals Pluto Team and community,
> >
> > I've staged a release candidate for the new Apache Portals Pluto 3.1.2
> 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
> >
> > Please review the release candidate for this project which is found in
> the following maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheportals-1027
> >
> > 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/projects/PLUTO/versions/12351085
> >
> > 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.1.2
> >
> > 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."
> >
> > Please review the release candidates and vote on releasing Apache
> Portals Pluto 3.1.2
> >
> > 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)
> >
> > Kind Regards,
> >
> > Neil
>

Reply via email to