pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Groschupf (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-34) Making Pig release ready
Date Thu, 28 Feb 2008 08:39:51 GMT

     [ https://issues.apache.org/jira/browse/PIG-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Stefan Groschupf updated PIG-34:

    Attachment: PIG-34_v_1.patch

This patch adds 
LICENSE.txt, NOTICE.txt and README.txt.
Also there is a new ant target (ant release) that also generates a md5 checksum file as requested
for the PMC release process.
I'm not a license expert but looks like the jars we use are all BSD license what would be
ok based on this reading:
However someone needs to double check that.

> 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_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.

View raw message