You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by "Ting(Goden) Yao" <ty...@pivotal.io> on 2015/11/03 01:04:15 UTC
Re: Propose an Apache HAWQ Release
Thanks for the feedback so far.
I've created release page at:
https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
to elaborate on the process, feel free to leave your comments there.
-Goden
On Wed, Oct 28, 2015 at 6:58 PM Lei Chang <ch...@gmail.com> wrote:
> There is a typo in the name (Semantic versioning has only three digits). it
> should be 2.0.0-beta-incubating
>
> Cheers
> Lei
>
>
> On Thu, Oct 29, 2015 at 1:27 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
>
> > As the first step of getting Apache HAWQ ready for its journey towards
> ASF
> > family, after some discussion with mentors, I'd like to propose a HAWQ
> > release in Nov 2015 and volunteer myself as the release manager.
> >
> > Here's a few details.
> >
> > - *Scope / Release Criteria*: Clear all potential IP issues in the
> > current code base and make it legally ready to be adopted by the
> > community.
> > - *Release Type*: Source code only, no binaries, but we'll make sure
> the
> > infrastructure is good to compile a build.
> > - *Release Version*: "2.0.0.0-beta-incubating"
> > - *Commit SHA*: TBD, depends on the IP cleanup and attribution work
> >
> > The process would be
> > 1. get the feedback from the community on the scope of the release (this
> > email)
> > 2. produce a release candidate source tarball
> > 3. start PPMC voting (re-spin if needed)
> > 4. start IPMC voting (re-spin if needed)
> >
> > Please reply if you have questions, concerns or other thoughts.
> >
> > Thanks.
> > -Goden
> >
>
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
Thanks for the comments on version names.
Hope this one won't cause issues as it's just a tarball release.
When I named the release tags, I was referring to a few other apache
projects and found some of them use "-RC" or "-incubating" in the tags.
We'll try to avoid that in the future releases.
-Goden
On Thu, Dec 24, 2015 at 9:47 AM Konstantin Boudnik <co...@apache.org> wrote:
> Returning from a bloody battle elseproject, I'd like to give a couple of
> words
> of caution. Producing releases that have dashes '-' in the version name is
> putting a lot of pressure on the downstream projects. The issue isn't
> apparent
> until you start producing linux packages. Debs would be fine, however RPMs
> because of their design shortcomings would be hard to build as '-' is
> prohibited in the version.
>
> Say, Bigtop would be directly affected by that if you guys ever want to be
> integrated in it.
>
> Besides, version literals aren't a good place to communicate semantics like
> 'alpha', 'beta' and so on. This is what Release Notes are for.
>
> Perhaps, more strict following of semver would be a good idea at until the
> community figure out the integration points with the rest of the ecosystem,
> etc.
>
> Looks like the RC will be respinning, so I will take a closer look at the
> release then. Cheers,
> Cos
>
> On Tue, Nov 03, 2015 at 12:04AM, Ting(Goden) Yao wrote:
> > Thanks for the feedback so far.
> > I've created release page at:
> >
> >
> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
> >
> > to elaborate on the process, feel free to leave your comments there.
> >
> > -Goden
> >
> >
> > On Wed, Oct 28, 2015 at 6:58 PM Lei Chang <ch...@gmail.com>
> wrote:
> >
> > > There is a typo in the name (Semantic versioning has only three
> digits). it
> > > should be 2.0.0-beta-incubating
> > >
> > > Cheers
> > > Lei
> > >
> > >
> > > On Thu, Oct 29, 2015 at 1:27 AM, Ting(Goden) Yao <ty...@pivotal.io>
> wrote:
> > >
> > > > As the first step of getting Apache HAWQ ready for its journey
> towards
> > > ASF
> > > > family, after some discussion with mentors, I'd like to propose a
> HAWQ
> > > > release in Nov 2015 and volunteer myself as the release manager.
> > > >
> > > > Here's a few details.
> > > >
> > > > - *Scope / Release Criteria*: Clear all potential IP issues in the
> > > > current code base and make it legally ready to be adopted by the
> > > > community.
> > > > - *Release Type*: Source code only, no binaries, but we'll make
> sure
> > > the
> > > > infrastructure is good to compile a build.
> > > > - *Release Version*: "2.0.0.0-beta-incubating"
> > > > - *Commit SHA*: TBD, depends on the IP cleanup and attribution
> work
> > > >
> > > > The process would be
> > > > 1. get the feedback from the community on the scope of the release
> (this
> > > > email)
> > > > 2. produce a release candidate source tarball
> > > > 3. start PPMC voting (re-spin if needed)
> > > > 4. start IPMC voting (re-spin if needed)
> > > >
> > > > Please reply if you have questions, concerns or other thoughts.
> > > >
> > > > Thanks.
> > > > -Goden
> > > >
> > >
>
Re: Propose an Apache HAWQ Release
Posted by Konstantin Boudnik <co...@apache.org>.
Returning from a bloody battle elseproject, I'd like to give a couple of words
of caution. Producing releases that have dashes '-' in the version name is
putting a lot of pressure on the downstream projects. The issue isn't apparent
until you start producing linux packages. Debs would be fine, however RPMs
because of their design shortcomings would be hard to build as '-' is
prohibited in the version.
Say, Bigtop would be directly affected by that if you guys ever want to be
integrated in it.
Besides, version literals aren't a good place to communicate semantics like
'alpha', 'beta' and so on. This is what Release Notes are for.
Perhaps, more strict following of semver would be a good idea at until the
community figure out the integration points with the rest of the ecosystem,
etc.
Looks like the RC will be respinning, so I will take a closer look at the
release then. Cheers,
Cos
On Tue, Nov 03, 2015 at 12:04AM, Ting(Goden) Yao wrote:
> Thanks for the feedback so far.
> I've created release page at:
>
> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
>
> to elaborate on the process, feel free to leave your comments there.
>
> -Goden
>
>
> On Wed, Oct 28, 2015 at 6:58 PM Lei Chang <ch...@gmail.com> wrote:
>
> > There is a typo in the name (Semantic versioning has only three digits). it
> > should be 2.0.0-beta-incubating
> >
> > Cheers
> > Lei
> >
> >
> > On Thu, Oct 29, 2015 at 1:27 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> >
> > > As the first step of getting Apache HAWQ ready for its journey towards
> > ASF
> > > family, after some discussion with mentors, I'd like to propose a HAWQ
> > > release in Nov 2015 and volunteer myself as the release manager.
> > >
> > > Here's a few details.
> > >
> > > - *Scope / Release Criteria*: Clear all potential IP issues in the
> > > current code base and make it legally ready to be adopted by the
> > > community.
> > > - *Release Type*: Source code only, no binaries, but we'll make sure
> > the
> > > infrastructure is good to compile a build.
> > > - *Release Version*: "2.0.0.0-beta-incubating"
> > > - *Commit SHA*: TBD, depends on the IP cleanup and attribution work
> > >
> > > The process would be
> > > 1. get the feedback from the community on the scope of the release (this
> > > email)
> > > 2. produce a release candidate source tarball
> > > 3. start PPMC voting (re-spin if needed)
> > > 4. start IPMC voting (re-spin if needed)
> > >
> > > Please reply if you have questions, concerns or other thoughts.
> > >
> > > Thanks.
> > > -Goden
> > >
> >
Re: Propose an Apache HAWQ Release
Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Dec 23, 2015 at 05:03PM, Roman Shaposhnik wrote:
> On Wed, Dec 23, 2015 at 4:56 PM, Noa Horn <nh...@pivotal.io> wrote:
> > Regarding 2 (gradle), thank you for the reference. I will open a JIRA for
> > it.
>
> Great!
>
> > Do we have to credit bigtop or can we just take the file as is?
>
> A line in NOTICE would be nice ;-)
As long as your copy stays under ASL2 terms - you're good ;)
Cos
Re: Propose an Apache HAWQ Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Wed, Dec 23, 2015 at 10:21 PM, Wen Lin <wl...@pivotal.io> wrote:
> Hi, Roman,
>
> For these lines, I can make it more specific to some subtree.
> <exclude>**/*.mk</exclude>
> <exclude>**/*.mak</exclude>
> <exclude>**/*.yaml</exclude>
> <exclude>**/*.m4</exclude>
> <exclude>config/*</exclude>
> <exclude>**/*.rc</exclude>
> <exclude>**/*.f</exclude>
> <exclude>**/Makefile*</exclude>
> For the other files, if it is too long to read, what do you suggest make it
> simple?
> For example, in src/backend/executor, some files belong to Postgres, some
> files belong to Apache in same directory.
>
> It is hard to write a wildcard expression which can exclude Postgres files,
> unless Iist all the files belong to Postgres in exclude file.
I've been thinking that perhaps we can automate the PG-derived
code detection process by including something like the snippet
bellow in pom.xml.
That'll give us part of the solution. Some of the files that were derived
from PG now carry Greenplum, EMC and Pivotal copyrights. For those
files an explicit ALv2 header will be required.
> There are a lot of similar situations like this. That's why the exclude
> list is very long.
> Do you have any idea for handling this?
Personally, I'd like to leverage RAT as much as possible here for
actually detecting licenses, not just excluding files. I know my
suggestion below may not be bullet proof, so I'd love to know
what other mentors think about it.
Thanks,
Roman.
RAT configuration snippet:
<licenses>
<license
implementation="org.apache.rat.analysis.license.SimplePatternBasedLicense">
<licenseFamilyCategory>PGSQL</licenseFamilyCategory>
<licenseFamilyName>PostgreSQL License</licenseFamilyName>
<notes></notes>
<patterns>
<pattern>$PostgreSQL:</pattern>
<pattern>PostgreSQL Global Development Group</pattern>
</patterns>
</license>
</licenses>
Re: Propose an Apache HAWQ Release
Posted by Wen Lin <wl...@pivotal.io>.
Hi, Roman,
For these lines, I can make it more specific to some subtree.
<exclude>**/*.mk</exclude>
<exclude>**/*.mak</exclude>
<exclude>**/*.yaml</exclude>
<exclude>**/*.m4</exclude>
<exclude>config/*</exclude>
<exclude>**/*.rc</exclude>
<exclude>**/*.f</exclude>
<exclude>**/Makefile*</exclude>
For the other files, if it is too long to read, what do you suggest make it
simple?
For example, in src/backend/executor, some files belong to Postgres, some
files belong to Apache in same directory.
It is hard to write a wildcard expression which can exclude Postgres files,
unless Iist all the files belong to Postgres in exclude file.
There are a lot of similar situations like this. That's why the exclude
list is very long.
Do you have any idea for handling this?
Thanks and Regards!
On Thu, Dec 24, 2015 at 12:09 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Wed, Dec 23, 2015 at 6:41 PM, Radar Da lei <rl...@pivotal.io> wrote:
> > Hi Roman,
> >
> > For item 0 and 1, I'm working on this, and there is a jira for it:
> > https://issues.apache.org/jira/browse/HAWQ-271
> >
> > These python source code will be removed, and user need to install them
> > before install hawq, maybe by using python pip install.
>
> Great! Seems like you guys are on a trajectory to take care of all the
> feedback I provided. I suggest once that is done you simply follow
> up with a more formal VOTE for RC3 as opposed to just doing the
> tagging.
>
> Btw, if may be a good idea to document the release steps on your
> wiki similar to how we did it for, lets say, Bigtop:
> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
>
> Thanks,
> Roman.
>
Re: Propose an Apache HAWQ Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Wed, Dec 23, 2015 at 6:41 PM, Radar Da lei <rl...@pivotal.io> wrote:
> Hi Roman,
>
> For item 0 and 1, I'm working on this, and there is a jira for it:
> https://issues.apache.org/jira/browse/HAWQ-271
>
> These python source code will be removed, and user need to install them
> before install hawq, maybe by using python pip install.
Great! Seems like you guys are on a trajectory to take care of all the
feedback I provided. I suggest once that is done you simply follow
up with a more formal VOTE for RC3 as opposed to just doing the
tagging.
Btw, if may be a good idea to document the release steps on your
wiki similar to how we did it for, lets say, Bigtop:
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
Thanks,
Roman.
Re: Propose an Apache HAWQ Release
Posted by Radar Da lei <rl...@pivotal.io>.
Hi Roman,
For item 0 and 1, I'm working on this, and there is a jira for it:
https://issues.apache.org/jira/browse/HAWQ-271
These python source code will be removed, and user need to install them
before install hawq, maybe by using python pip install.
Thanks.
Regards,
Radar
On Thu, Dec 24, 2015 at 9:03 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Wed, Dec 23, 2015 at 4:56 PM, Noa Horn <nh...@pivotal.io> wrote:
> > Regarding 2 (gradle), thank you for the reference. I will open a JIRA for
> > it.
>
> Great!
>
> > Do we have to credit bigtop or can we just take the file as is?
>
> A line in NOTICE would be nice ;-)
>
> Thanks,
> Roman.
>
Re: Propose an Apache HAWQ Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Wed, Dec 23, 2015 at 4:56 PM, Noa Horn <nh...@pivotal.io> wrote:
> Regarding 2 (gradle), thank you for the reference. I will open a JIRA for
> it.
Great!
> Do we have to credit bigtop or can we just take the file as is?
A line in NOTICE would be nice ;-)
Thanks,
Roman.
Re: Propose an Apache HAWQ Release
Posted by Noa Horn <nh...@pivotal.io>.
Regarding 2 (gradle), thank you for the reference. I will open a JIRA for
it.
Do we have to credit bigtop or can we just take the file as is?
On Wed, Dec 23, 2015 at 4:39 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Fri, Dec 18, 2015 at 11:04 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> > I just tagged "2.0.0-beta-incubating-RC2" based on latest commit:
> >
> https://github.com/apache/incubator-hawq/commit/b6cb39c37e83fb5ee542b9f953c3a5e28e4617eb
>
> This looks *much* better than RC1. Great progress, team!
>
> Still a few things are left that need to be addressed:
> 0. Content of tools/bin/pythonSrc doesn't look good to me.
> There's GPL stuff in there that absolutely MUST be purged
> from our repo. There are a few things under MIT and BSD
> licenses in there as well, but since you will have to come up
> with a solution for GPL archives you may as well get rid of
> all of them.
>
> 1. netperf-2.4.3.tar.gz needs to be removed. It is under a specific
> license from HP and we can't carry it in the tarball release of HAWQ
>
> 2. I still think that we need to get rid of Gradle jar. In order to
> solve
> boostraping problem you can either use the approach Bigtop is taking:
> https://github.com/apache/bigtop/blob/master/gradlew#L18
> (just replace your gradelw with Bigtop's). Or you can mandate Gradle.
>
> 3. I really appreciate RAT integration, but looking at the exclude list
> I don't think the following belongs there:
> <exclude>**/*.mk</exclude>
> <exclude>**/*.mak</exclude>
> <exclude>**/*.yaml</exclude>
> <exclude>**/*.m4</exclude>
> <exclude>config/*</exclude>
> <exclude>**/*.rc</exclude>
> <exclude>**/*.f</exclude>
> <exclude>**/Makefile*</exclude>
> Instead of wholesale exclusion like that I'd like to see exclusion
> based on
> subtrees of the source tree. IOW, if a file that matches one of the
> above
> masks comes from PG just mark it so and mark a folder. Excluding a whole
> class of files based on extension makes RAT less useful in the future.
>
> 4. In general, I'd like to see the exclude list for RAT be more
> structured
> and concise. It is currently 446 entries long and pretty much impossible
> to review properly.
>
> Thanks,
> Roman.
>
Re: Propose an Apache HAWQ Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Dec 18, 2015 at 11:04 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> I just tagged "2.0.0-beta-incubating-RC2" based on latest commit:
> https://github.com/apache/incubator-hawq/commit/b6cb39c37e83fb5ee542b9f953c3a5e28e4617eb
This looks *much* better than RC1. Great progress, team!
Still a few things are left that need to be addressed:
0. Content of tools/bin/pythonSrc doesn't look good to me.
There's GPL stuff in there that absolutely MUST be purged
from our repo. There are a few things under MIT and BSD
licenses in there as well, but since you will have to come up
with a solution for GPL archives you may as well get rid of
all of them.
1. netperf-2.4.3.tar.gz needs to be removed. It is under a specific
license from HP and we can't carry it in the tarball release of HAWQ
2. I still think that we need to get rid of Gradle jar. In order to solve
boostraping problem you can either use the approach Bigtop is taking:
https://github.com/apache/bigtop/blob/master/gradlew#L18
(just replace your gradelw with Bigtop's). Or you can mandate Gradle.
3. I really appreciate RAT integration, but looking at the exclude list
I don't think the following belongs there:
<exclude>**/*.mk</exclude>
<exclude>**/*.mak</exclude>
<exclude>**/*.yaml</exclude>
<exclude>**/*.m4</exclude>
<exclude>config/*</exclude>
<exclude>**/*.rc</exclude>
<exclude>**/*.f</exclude>
<exclude>**/Makefile*</exclude>
Instead of wholesale exclusion like that I'd like to see exclusion based on
subtrees of the source tree. IOW, if a file that matches one of the above
masks comes from PG just mark it so and mark a folder. Excluding a whole
class of files based on extension makes RAT less useful in the future.
4. In general, I'd like to see the exclude list for RAT be more structured
and concise. It is currently 446 entries long and pretty much impossible
to review properly.
Thanks,
Roman.
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
I just tagged "2.0.0-beta-incubating-RC2" based on latest commit:
https://github.com/apache/incubator-hawq/commit/b6cb39c37e83fb5ee542b9f953c3a5e28e4617eb
Please mentors review and provide feedback.
-Goden
On Tue, Nov 24, 2015 at 10:09 AM Ting(Goden) Yao <ty...@pivotal.io> wrote:
> Just correct the typos : they are HAWQ-183, HAWQ-184, HAWQ-185 and
> HAWQ-186 to track all the new issues Roman discovered for
> 2.0.0-beta-incubating release.
> I've updated release page with the latest info.
>
> On Mon, Nov 23, 2015 at 11:57 PM Lei Chang <ch...@gmail.com> wrote:
>
>> Good catch. HAWQ-1863 HAWQ-1864 HAWQ-1865 HAWQ-1866 are used to track
>> this.
>>
>> Cheers
>> Lei
>>
>>
>> On Tue, Nov 24, 2015 at 12:37 PM, Roman Shaposhnik <ro...@shaposhnik.org>
>> wrote:
>>
>> > On Mon, Nov 23, 2015 at 12:45 PM, Ting(Goden) Yao <ty...@pivotal.io>
>> wrote:
>> > > Yes I meant "RC1" , missed typing it in the previous email.
>> >
>> > Great! My cursory look at the tag produced the following:
>> > 1. We need to add the DISCLAIMER file
>> > 2. There are a few things checked into the source tree that
>> > definitely shouldn't be in the release tarball:
>> > * anythings that's *.tar.gz
>> > * anything that's a dependency jar
>> > * ./depends/libyarn/releng/bin/templates/.core-site-secure-ha.xml.swp
>> > * ./pxf/gradle/wrapper/gradle-wrapper.jar
>> > * ./contrib/hawq-hadoop/hawq-mapreduce-tool/lib/*.jar
>> > * ./src/test/regress/data/pxf/*.class
>> > * ./src/test/regress/data/pxf/*.class
>> > * ./tools/bin/ext/yaml/*.pyc
>> >
>> > 3. There are a few things that I'd like to understand
>> > why they are there:
>> > * ./depends/libyarn/releng/make/dependencies/cacerts
>> >
>> > Finally (and somewhat surprisingly) the RAT check turned out
>> > to be pretty alarming. I thought that you guys took care of
>> > the licensing headers some time ago. Am I misremembering?
>> >
>> > Anyway, here's how to reproduce and marvel at "5030 Unknown Licenses".
>> >
>> > $ java -jar ~/src/apache/rat-0.11/apache-rat-0.11.jar .
>> >
>> > *****************************************************
>> > Summary
>> > -------
>> > Generated at: 2015-11-23T19:40:00-08:00
>> > Notes: 79
>> > Binaries: 789
>> > Archives: 20
>> > Standards: 5871
>> >
>> > Apache Licensed: 825
>> > Generated Documents: 0
>> >
>> > JavaDocs are generated and so license header is optional
>> > Generated files do not required license headers
>> >
>> > 5030 Unknown Licenses
>> >
>> > *******************************
>> >
>>
>
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
Just correct the typos : they are HAWQ-183, HAWQ-184, HAWQ-185 and HAWQ-186
to track all the new issues Roman discovered for 2.0.0-beta-incubating
release.
I've updated release page with the latest info.
On Mon, Nov 23, 2015 at 11:57 PM Lei Chang <ch...@gmail.com> wrote:
> Good catch. HAWQ-1863 HAWQ-1864 HAWQ-1865 HAWQ-1866 are used to track this.
>
> Cheers
> Lei
>
>
> On Tue, Nov 24, 2015 at 12:37 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > On Mon, Nov 23, 2015 at 12:45 PM, Ting(Goden) Yao <ty...@pivotal.io>
> wrote:
> > > Yes I meant "RC1" , missed typing it in the previous email.
> >
> > Great! My cursory look at the tag produced the following:
> > 1. We need to add the DISCLAIMER file
> > 2. There are a few things checked into the source tree that
> > definitely shouldn't be in the release tarball:
> > * anythings that's *.tar.gz
> > * anything that's a dependency jar
> > * ./depends/libyarn/releng/bin/templates/.core-site-secure-ha.xml.swp
> > * ./pxf/gradle/wrapper/gradle-wrapper.jar
> > * ./contrib/hawq-hadoop/hawq-mapreduce-tool/lib/*.jar
> > * ./src/test/regress/data/pxf/*.class
> > * ./src/test/regress/data/pxf/*.class
> > * ./tools/bin/ext/yaml/*.pyc
> >
> > 3. There are a few things that I'd like to understand
> > why they are there:
> > * ./depends/libyarn/releng/make/dependencies/cacerts
> >
> > Finally (and somewhat surprisingly) the RAT check turned out
> > to be pretty alarming. I thought that you guys took care of
> > the licensing headers some time ago. Am I misremembering?
> >
> > Anyway, here's how to reproduce and marvel at "5030 Unknown Licenses".
> >
> > $ java -jar ~/src/apache/rat-0.11/apache-rat-0.11.jar .
> >
> > *****************************************************
> > Summary
> > -------
> > Generated at: 2015-11-23T19:40:00-08:00
> > Notes: 79
> > Binaries: 789
> > Archives: 20
> > Standards: 5871
> >
> > Apache Licensed: 825
> > Generated Documents: 0
> >
> > JavaDocs are generated and so license header is optional
> > Generated files do not required license headers
> >
> > 5030 Unknown Licenses
> >
> > *******************************
> >
>
Re: Propose an Apache HAWQ Release
Posted by Lei Chang <ch...@gmail.com>.
Good catch. HAWQ-1863 HAWQ-1864 HAWQ-1865 HAWQ-1866 are used to track this.
Cheers
Lei
On Tue, Nov 24, 2015 at 12:37 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Mon, Nov 23, 2015 at 12:45 PM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> > Yes I meant "RC1" , missed typing it in the previous email.
>
> Great! My cursory look at the tag produced the following:
> 1. We need to add the DISCLAIMER file
> 2. There are a few things checked into the source tree that
> definitely shouldn't be in the release tarball:
> * anythings that's *.tar.gz
> * anything that's a dependency jar
> * ./depends/libyarn/releng/bin/templates/.core-site-secure-ha.xml.swp
> * ./pxf/gradle/wrapper/gradle-wrapper.jar
> * ./contrib/hawq-hadoop/hawq-mapreduce-tool/lib/*.jar
> * ./src/test/regress/data/pxf/*.class
> * ./src/test/regress/data/pxf/*.class
> * ./tools/bin/ext/yaml/*.pyc
>
> 3. There are a few things that I'd like to understand
> why they are there:
> * ./depends/libyarn/releng/make/dependencies/cacerts
>
> Finally (and somewhat surprisingly) the RAT check turned out
> to be pretty alarming. I thought that you guys took care of
> the licensing headers some time ago. Am I misremembering?
>
> Anyway, here's how to reproduce and marvel at "5030 Unknown Licenses".
>
> $ java -jar ~/src/apache/rat-0.11/apache-rat-0.11.jar .
>
> *****************************************************
> Summary
> -------
> Generated at: 2015-11-23T19:40:00-08:00
> Notes: 79
> Binaries: 789
> Archives: 20
> Standards: 5871
>
> Apache Licensed: 825
> Generated Documents: 0
>
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
>
> 5030 Unknown Licenses
>
> *******************************
>
Re: Propose an Apache HAWQ Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Nov 23, 2015 at 12:45 PM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> Yes I meant "RC1" , missed typing it in the previous email.
Great! My cursory look at the tag produced the following:
1. We need to add the DISCLAIMER file
2. There are a few things checked into the source tree that
definitely shouldn't be in the release tarball:
* anythings that's *.tar.gz
* anything that's a dependency jar
* ./depends/libyarn/releng/bin/templates/.core-site-secure-ha.xml.swp
* ./pxf/gradle/wrapper/gradle-wrapper.jar
* ./contrib/hawq-hadoop/hawq-mapreduce-tool/lib/*.jar
* ./src/test/regress/data/pxf/*.class
* ./src/test/regress/data/pxf/*.class
* ./tools/bin/ext/yaml/*.pyc
3. There are a few things that I'd like to understand
why they are there:
* ./depends/libyarn/releng/make/dependencies/cacerts
Finally (and somewhat surprisingly) the RAT check turned out
to be pretty alarming. I thought that you guys took care of
the licensing headers some time ago. Am I misremembering?
Anyway, here's how to reproduce and marvel at "5030 Unknown Licenses".
$ java -jar ~/src/apache/rat-0.11/apache-rat-0.11.jar .
*****************************************************
Summary
-------
Generated at: 2015-11-23T19:40:00-08:00
Notes: 79
Binaries: 789
Archives: 20
Standards: 5871
Apache Licensed: 825
Generated Documents: 0
JavaDocs are generated and so license header is optional
Generated files do not required license headers
5030 Unknown Licenses
*******************************
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
Yes I meant "RC1" , missed typing it in the previous email.
On Sat, Nov 21, 2015 at 11:17 AM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Fri, Nov 20, 2015 at 10:49 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> > Just a quick update:
> > Tag has been pushed to master "2.0.0-beta-incubating".
>
> This would be an extremely BAD choice of naming for the tag
> until what it points to actually gets releases. Luckily, I think
> you meant the RC1 one:
> https://github.com/apache/incubator-hawq/tags
>
> Please ONLY EVER use release names for the tags
> once they fully get approved by PPMC and IPMC after
> a full vote.
>
> > We'll start voting process early next week.
> > Details please refer to:
> >
> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
>
> Great! I'll give the RC1 tag a preliminary review on Mon
> and hopefully other mentors can start providing their
> feedback as well.
>
> Thanks,
> Roman.
>
Re: Propose an Apache HAWQ Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Nov 20, 2015 at 10:49 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
> Just a quick update:
> Tag has been pushed to master "2.0.0-beta-incubating".
This would be an extremely BAD choice of naming for the tag
until what it points to actually gets releases. Luckily, I think
you meant the RC1 one:
https://github.com/apache/incubator-hawq/tags
Please ONLY EVER use release names for the tags
once they fully get approved by PPMC and IPMC after
a full vote.
> We'll start voting process early next week.
> Details please refer to:
> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
Great! I'll give the RC1 tag a preliminary review on Mon
and hopefully other mentors can start providing their
feedback as well.
Thanks,
Roman.
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
Just a quick update:
Tag has been pushed to master "2.0.0-beta-incubating".
We'll start voting process early next week.
Details please refer to:
https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
-Goden
On Tue, Nov 17, 2015 at 5:58 PM Ting(Goden) Yao <ty...@pivotal.io> wrote:
> We've decided to use
> https://github.com/apache/incubator-hawq/commit/be9a74bea5181fcea9b14e885a2de5d9089e1b02 as
> beta-RC1 commit.
> I'll tag the master branch shortly and you're ok to continue your work.
> Master is unblocked.
>
> Thanks
> -Goden
>
>
> On Mon, Nov 16, 2015 at 3:52 PM Ting(Goden) Yao <ty...@pivotal.io> wrote:
>
>> Hi,
>> We're very close to cutting the Apache HAWQ 2.0.0-beta-incubating
>> <https://issues.apache.org/jira/browse/HAWQ/fixforversion/12334000>
>> release.
>> As part of the release process, I'd like to* ask everyone to hold off
>> your commits* unless it's linked to a JIRA with 2.0.0-beta-incubating
>> <https://issues.apache.org/jira/browse/HAWQ/fixforversion/12334000> tag.
>>
>> I'm going to tag the master branch with "2.0.0-beta-incubating-RC1". And
>> we'll follow https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+
>> Release+2.0.0-beta-incubating for the rest of the process.
>>
>> Thanks
>> -Goden
>>
>> On Mon, Nov 2, 2015 at 4:04 PM Ting(Goden) Yao <ty...@pivotal.io> wrote:
>>
>>> Thanks for the feedback so far.
>>> I've created release page at:
>>>
>>> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
>>>
>>> to elaborate on the process, feel free to leave your comments there.
>>>
>>> -Goden
>>>
>>>
>>> On Wed, Oct 28, 2015 at 6:58 PM Lei Chang <ch...@gmail.com>
>>> wrote:
>>>
>>>> There is a typo in the name (Semantic versioning has only three
>>>> digits). it
>>>> should be 2.0.0-beta-incubating
>>>>
>>>> Cheers
>>>> Lei
>>>>
>>>>
>>>> On Thu, Oct 29, 2015 at 1:27 AM, Ting(Goden) Yao <ty...@pivotal.io>
>>>> wrote:
>>>>
>>>> > As the first step of getting Apache HAWQ ready for its journey
>>>> towards ASF
>>>> > family, after some discussion with mentors, I'd like to propose a HAWQ
>>>> > release in Nov 2015 and volunteer myself as the release manager.
>>>> >
>>>> > Here's a few details.
>>>> >
>>>> > - *Scope / Release Criteria*: Clear all potential IP issues in the
>>>> > current code base and make it legally ready to be adopted by the
>>>> > community.
>>>> > - *Release Type*: Source code only, no binaries, but we'll make
>>>> sure the
>>>> > infrastructure is good to compile a build.
>>>> > - *Release Version*: "2.0.0.0-beta-incubating"
>>>> > - *Commit SHA*: TBD, depends on the IP cleanup and attribution work
>>>> >
>>>> > The process would be
>>>> > 1. get the feedback from the community on the scope of the release
>>>> (this
>>>> > email)
>>>> > 2. produce a release candidate source tarball
>>>> > 3. start PPMC voting (re-spin if needed)
>>>> > 4. start IPMC voting (re-spin if needed)
>>>> >
>>>> > Please reply if you have questions, concerns or other thoughts.
>>>> >
>>>> > Thanks.
>>>> > -Goden
>>>> >
>>>>
>>>
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
We've decided to use
https://github.com/apache/incubator-hawq/commit/be9a74bea5181fcea9b14e885a2de5d9089e1b02
as
beta-RC1 commit.
I'll tag the master branch shortly and you're ok to continue your work.
Master is unblocked.
Thanks
-Goden
On Mon, Nov 16, 2015 at 3:52 PM Ting(Goden) Yao <ty...@pivotal.io> wrote:
> Hi,
> We're very close to cutting the Apache HAWQ 2.0.0-beta-incubating
> <https://issues.apache.org/jira/browse/HAWQ/fixforversion/12334000>
> release.
> As part of the release process, I'd like to* ask everyone to hold off
> your commits* unless it's linked to a JIRA with 2.0.0-beta-incubating
> <https://issues.apache.org/jira/browse/HAWQ/fixforversion/12334000> tag.
>
> I'm going to tag the master branch with "2.0.0-beta-incubating-RC1". And
> we'll follow https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+
> Release+2.0.0-beta-incubating for the rest of the process.
>
> Thanks
> -Goden
>
> On Mon, Nov 2, 2015 at 4:04 PM Ting(Goden) Yao <ty...@pivotal.io> wrote:
>
>> Thanks for the feedback so far.
>> I've created release page at:
>>
>> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
>>
>> to elaborate on the process, feel free to leave your comments there.
>>
>> -Goden
>>
>>
>> On Wed, Oct 28, 2015 at 6:58 PM Lei Chang <ch...@gmail.com> wrote:
>>
>>> There is a typo in the name (Semantic versioning has only three digits).
>>> it
>>> should be 2.0.0-beta-incubating
>>>
>>> Cheers
>>> Lei
>>>
>>>
>>> On Thu, Oct 29, 2015 at 1:27 AM, Ting(Goden) Yao <ty...@pivotal.io>
>>> wrote:
>>>
>>> > As the first step of getting Apache HAWQ ready for its journey towards
>>> ASF
>>> > family, after some discussion with mentors, I'd like to propose a HAWQ
>>> > release in Nov 2015 and volunteer myself as the release manager.
>>> >
>>> > Here's a few details.
>>> >
>>> > - *Scope / Release Criteria*: Clear all potential IP issues in the
>>> > current code base and make it legally ready to be adopted by the
>>> > community.
>>> > - *Release Type*: Source code only, no binaries, but we'll make
>>> sure the
>>> > infrastructure is good to compile a build.
>>> > - *Release Version*: "2.0.0.0-beta-incubating"
>>> > - *Commit SHA*: TBD, depends on the IP cleanup and attribution work
>>> >
>>> > The process would be
>>> > 1. get the feedback from the community on the scope of the release
>>> (this
>>> > email)
>>> > 2. produce a release candidate source tarball
>>> > 3. start PPMC voting (re-spin if needed)
>>> > 4. start IPMC voting (re-spin if needed)
>>> >
>>> > Please reply if you have questions, concerns or other thoughts.
>>> >
>>> > Thanks.
>>> > -Goden
>>> >
>>>
>>
Re: Propose an Apache HAWQ Release
Posted by "Ting(Goden) Yao" <ty...@pivotal.io>.
Hi,
We're very close to cutting the Apache HAWQ 2.0.0-beta-incubating
<https://issues.apache.org/jira/browse/HAWQ/fixforversion/12334000> release.
As part of the release process, I'd like to* ask everyone to hold off your
commits* unless it's linked to a JIRA with 2.0.0-beta-incubating
<https://issues.apache.org/jira/browse/HAWQ/fixforversion/12334000> tag.
I'm going to tag the master branch with "2.0.0-beta-incubating-RC1". And
we'll follow https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release
+2.0.0-beta-incubating for the rest of the process.
Thanks
-Goden
On Mon, Nov 2, 2015 at 4:04 PM Ting(Goden) Yao <ty...@pivotal.io> wrote:
> Thanks for the feedback so far.
> I've created release page at:
>
> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0-beta-incubating
>
> to elaborate on the process, feel free to leave your comments there.
>
> -Goden
>
>
> On Wed, Oct 28, 2015 at 6:58 PM Lei Chang <ch...@gmail.com> wrote:
>
>> There is a typo in the name (Semantic versioning has only three digits).
>> it
>> should be 2.0.0-beta-incubating
>>
>> Cheers
>> Lei
>>
>>
>> On Thu, Oct 29, 2015 at 1:27 AM, Ting(Goden) Yao <ty...@pivotal.io> wrote:
>>
>> > As the first step of getting Apache HAWQ ready for its journey towards
>> ASF
>> > family, after some discussion with mentors, I'd like to propose a HAWQ
>> > release in Nov 2015 and volunteer myself as the release manager.
>> >
>> > Here's a few details.
>> >
>> > - *Scope / Release Criteria*: Clear all potential IP issues in the
>> > current code base and make it legally ready to be adopted by the
>> > community.
>> > - *Release Type*: Source code only, no binaries, but we'll make sure
>> the
>> > infrastructure is good to compile a build.
>> > - *Release Version*: "2.0.0.0-beta-incubating"
>> > - *Commit SHA*: TBD, depends on the IP cleanup and attribution work
>> >
>> > The process would be
>> > 1. get the feedback from the community on the scope of the release
>> (this
>> > email)
>> > 2. produce a release candidate source tarball
>> > 3. start PPMC voting (re-spin if needed)
>> > 4. start IPMC voting (re-spin if needed)
>> >
>> > Please reply if you have questions, concerns or other thoughts.
>> >
>> > Thanks.
>> > -Goden
>> >
>>
>