[
https://issues.apache.org/jira/browse/PIG-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575346#action_12575346
]
Benjamin Francisoud commented on PIG-34:
----------------------------------------
Olga> yes I do also prefer PIG-111 to be commited that this one ;)
Pi Song> According to the license:
{quote}
Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
{quote}
I suppose if we include a jsch-license.txt in pig release jar, we would be
meeting jsch license terms, wdyt ?
> Making Pig release ready
> ------------------------
>
> Key: PIG-34
> URL: https://issues.apache.org/jira/browse/PIG-34
> Project: Pig
> Issue Type: New Feature
> Reporter: Olga Natkovich
> Assignee: Olga Natkovich
> Attachments: PIG-34-v02.patch, PIG-34_v_1.patch
>
>
> This is from email on pig-dev from Bertrand Delacretaz:
> I wrote a blog post [3] while mentoring Wicket, it might help as an overview.
> > ...I found some online documents
> > (http://incubator.apache.org/guides/releasemanagement.htm) about it
> > but I don't have a very good feel for what is the minimal set of
> > things we need to do to get ready....
> I'd say the minimal set is
> 1) Check that the required external libraries (if any) can be distributed,
> see [2]
> 2) Create the required NOTICE and LICENSE files, see [1] and [2]
> 3) Generate distribution artifacts which include this info
> 4) Call for review of these artifacts, followed by a vote here and then a
> vote by the Incubator PMC.
> -Bertrand
> [1] http://incubator.apache.org/guides/releasemanagement.html
> [2] http://people.apache.org/~cliffs/3party.html
> [3] http://www.codeconsult.ch/bertrand/archives/000759.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
