Hi Neil,
On Wed, May 16, 2018 at 5:48 PM, Neil Griffin
wrote:
> Hi Woonsan,
>
> Step 12 is "Release the bundle Zip file"
> https://github.com/apache/portals-pluto/blob/master/RELEASE-PROCEDURE.txt#L129-L146
>
> And Step 13 is "PUT THE RELEASE CANDIDATE UP FOR A VOTE"
> https://github.com/apache/p
Hi Neil,
Thank you very much for the elaborated answers.
I think the only thing required as minimum is to upload the
pluto-3.0.1-source-release.zip and its signature files (.asc, .sha) to
https://dist.apache.org/repos/dist/dev/portals/pluto/pluto-3.0.1/, and
put the link to the directory containi
By the way, I'm not trying to block the way. ;-) I'm just trying to
make a right release (process) this time.
Please let me know if I can help with anything. I'll help to fix the
(minimal) things to make a release as soon as possible. :-)
Regards,
Woonsan
On Mon, May 14, 2018 at 11:39 AM, Woons
Yes, please remove the profile. We cannot use LGPL-like dependency in
our source.
Regards,
Woonsan
On Mon, May 14, 2018 at 10:45 AM, Neil Griffin
wrote:
> Regarding the "liferay" profile, it is a profile that is not required to be
> specified for building the TCK on Pluto.
>
> If that is not su
On Mon, May 14, 2018 at 10:43 AM, Neil Griffin
wrote:
> Hi Woonsan,
>
> We followed the same process as we did for the 3.0.0 release.
>
> The "building from source" requirement would be accomplished by building
> source from a Git tag.
I don't think a Git tag can replace the requirement of a "val
-1
I couldn't find pluto-3.0.1 tag in
https://git-wip-us.apache.org/repos/asf/portals-pluto.git. I wonder
how the release candidate artifacts were made. The master branch's
version was not bumped up to 3.0.2-SNAPSHOT either.
Even worse, there's a stopper in the root pom.xml [1]:
lifera
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 wrote:
> Dear Apache Portals Pluto Team and community,
>
> I've staged a release candidate for the new Apache Po
Hi,
I'm not sure if the release includes the source packages properly.
"The fundamental requirement for a release is that it consist of the
necessary source code to build the project." [1]
See my comments inline for each package.
[1] http://www.apache.org/dev/release-publishing.html
On Fri, May
