[
https://issues.apache.org/jira/browse/PARQUET-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Blue updated PARQUET-111:
------------------------------
Description:
In order to get release 1.6 of parquet-mr out, we have to do some updates.
For Apache policy:
1. -Update the header in all Parquet source files (see PARQUET-72 for examples)-
2. -Add DISCLAIMER and KEYS files (copy from parquet-format)-
3. -Add the Apache Rat maven plugin to check source file license headers and
make sure it passes-
4. -For the overall project, go through any external source that is bundled and
update the root LICENSE and NOTICE files-
5. -For each module that produces a binary artifact, go through the content
pulled in by the maven-shade-plugin or the maven-assembly-plugin and update a
LICENSE and NOTICE file for that content (see PARQUET-109 for an example).-
We also need to update the build (see [PR
#11|https://github.com/apache/incubator-parquet-format/pull/11]):
1. -Inherit from the ASF pom- to pull in Apache release settings (will be done
for org.apache groupId)
2. -Update metadata, like SCM, mailing lists, and JIRA links-
3. -Go through modules and remove any LICENSE and NOTICE files that are
included by shading or assembly (relevant content should be included in
parquet-mr LICENSE and NOTICE)-
was:
In order to get release 1.6 of parquet-mr out, we have to do some updates.
For Apache policy:
1. -Update the header in all Parquet source files (see PARQUET-72 for examples)-
2. -Add DISCLAIMER and KEYS files (copy from parquet-format)-
3. -Add the Apache Rat maven plugin to check source file license headers and
make sure it passes-
4. -For the overall project, go through any external source that is bundled and
update the root LICENSE and NOTICE files-
5. -For each module that produces a binary artifact, go through the content
pulled in by the maven-shade-plugin or the maven-assembly-plugin and update a
LICENSE and NOTICE file for that content (see PARQUET-109 for an example).-
We also need to update the build (see [PR
#11|https://github.com/apache/incubator-parquet-format/pull/11]):
1. -Inherit from the ASF pom- to pull in Apache release settings (will be done
for org.apache groupId)
2. -Update metadata, like SCM, mailing lists, and JIRA links-
3. Go through modules and remove any LICENSE and NOTICE files that are included
by shading or assembly (relevant content should be included in parquet-mr
LICENSE and NOTICE)
> Tasks for parquet-mr 1.6.0 release
> ----------------------------------
>
> Key: PARQUET-111
> URL: https://issues.apache.org/jira/browse/PARQUET-111
> Project: Parquet
> Issue Type: Task
> Components: parquet-mr
> Reporter: Ryan Blue
> Assignee: Ryan Blue
>
> In order to get release 1.6 of parquet-mr out, we have to do some updates.
> For Apache policy:
> 1. -Update the header in all Parquet source files (see PARQUET-72 for
> examples)-
> 2. -Add DISCLAIMER and KEYS files (copy from parquet-format)-
> 3. -Add the Apache Rat maven plugin to check source file license headers and
> make sure it passes-
> 4. -For the overall project, go through any external source that is bundled
> and update the root LICENSE and NOTICE files-
> 5. -For each module that produces a binary artifact, go through the content
> pulled in by the maven-shade-plugin or the maven-assembly-plugin and update a
> LICENSE and NOTICE file for that content (see PARQUET-109 for an example).-
> We also need to update the build (see [PR
> #11|https://github.com/apache/incubator-parquet-format/pull/11]):
> 1. -Inherit from the ASF pom- to pull in Apache release settings (will be
> done for org.apache groupId)
> 2. -Update metadata, like SCM, mailing lists, and JIRA links-
> 3. -Go through modules and remove any LICENSE and NOTICE files that are
> included by shading or assembly (relevant content should be included in
> parquet-mr LICENSE and NOTICE)-
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
