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 <[email protected]>
wrote:
> On Wed, Dec 23, 2015 at 6:41 PM, Radar Da lei <[email protected]> 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.
>
