Re: [VOTE] Release Apache Portals Pluto 3.0.0

Werner Keil <[email protected]>
Newsgroups gmane.comp.jakarta.pluto.devel
Message-ID <CAAGawe0jtqE+0HaMTS7fv-VLtHLFxxdvGHniQq5hyDVGAk9wbA@mail.gmail.com>
+1

There is a Jenkins build failure right now. I assume it is not blocking the
release, does it?

Regards,

Werner


On Fri, Jan 6, 2017 at 1:21 AM, DavidSeanTaylor <[email protected]>
wrote:

> Good catch Woonsan.
>
> I see for example these links are broken:
>
> http://localhost:8080/pluto/portal/Test%20Page
> http://localhost:8080/pluto/portal/JSR%20286%20Tests
>
> I agree these should be fixed, but those tests are not part of the
> official TCK. IMO it should not hold up the release.
>
> On Jan 5, 2017, at 12:45 PM, Woonsan Ko <[email protected]> wrote:
>
> +1 for Release.
>
> I don't think this can block the release, but just FYI, when I run the
> tomcat8 bundle zip locally, I observe the following TCK tests failing:
> - Test Portlet: #14. Security Mapping Test
> - JSR 286 Tests: #3. EventFilterTest: PLT [unknown] -
> checkTriggerEventFromActionPhase
> - JSR 286 Tests: #4. SimplePayloadEventTest: PLT 15.2.3 -
> checkFireEventsFromActionPhase
> - JSR 286 Tests: # 5.Complex Payload Event Test: PLT 15.2.3 -
> checkFireEventsFromActionPhase
> - JSR 286 Tests: # 6.Public Render Parameter Test
>
> Are those known?
>
> Regards,
>
> Woonsan
>
>
> On Thu, Jan 5, 2017 at 3:09 PM, DavidSeanTaylor <[email protected]>
> wrote:
>
> 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
>
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.