I guess we also have to vote on it (at least PMC members with binding votes)
Werner On Mon, Apr 3, 2017 at 11:52 PM, Neil Griffin <[email protected] > wrote: > @Woonsan: OK that's good. Thanks for letting me know. > > @All: Please do a code review of the commit and let me know if these two > archetypes are acceptable. I'll send an email to our PMC on Wednesday after > I have incorporated any feedback. > > Thanks, > > Neil > > > On 4/3/17 5:35 PM, Woonsan Ko wrote: > >> Hi Neil, >> >> I think that archetype artifact qualifies as an Apache release [1]. >> So, I think it needs to go through the normal release process. >> >> Regards, >> >> Woonsan >> >> [1] http://www.apache.org/dev/release-publishing.html#goal >> >> >> On Mon, Apr 3, 2017 at 5:18 PM, Neil Griffin >> <[email protected]> wrote: >> >>> Dear friends of Pluto, >>> >>> I recently created the following issue: >>> PLUTO-655: Maven archetypes for Portlet 3.0 >>> https://issues.apache.org/jira/browse/PLUTO-655 >>> >>> And then pushed the following commit: >>> https://github.com/apache/portals-pluto/commit/4f89abbc1e2bc >>> 781126c61a63dec2c4c3694456a >>> >>> I'd like to release these archetypes to Maven Central. Does this need to >>> go >>> through the normal release voting process, or could this be considered >>> to be >>> a supplementary feature that can be released independently? >>> >>> >>> Thanks, >>> >>> Neil >>> >>> >>
