RE: Proposal to add hive regression tests to check-PR tests

[Liu, Ming (Ming)]

+1 to this

-Original Message-
From: Selva Govindarajan [mailto:selva.govindara...@esgyn.com] 
Sent: Saturday, July 16, 2016 9:08 AM
To: dev@trafodion.incubator.apache.org
Subject: Proposal to add hive regression tests to check-PR tests

If you have subscribed to Trafodion Daily Build, you would have noticed that 
the daily build has been failing for some days. Most often, it is due the 
failure in hive regression tests run as part of the daily build.
Lately, there has been some conscious effort made successfully to ensure that 
the hive regression tests can be run reliably. To maintain the Trafodion daily 
build in that state, I am proposing to include hive regressions to check-PR 
tests.  It shouldn’t add the overall time taken to regressions tests because 
tests are run in parallel on different VMs, though it would consume more 
resources.



-  Selva

Re: Chinese Contributor Access

[Carol Pearson]

Do we have a Chinese translation of the Contributor Guide, tested and
validated by one of our current Chinese contributors?  If not, that sounds
like the first place to start.

-Carol P.

---
Email:carol.pearson...@gmail.com
Twitter:  @CarolP222
---

On Fri, Jul 15, 2016 at 8:19 AM, Gunnar Tapper 
wrote:

> Hi Felix,
>
> The documentation is part of the source code. You need to set up a build
> environment and use the structure in the docs directory to build/create a
> new document.
>
> So, the "click a button to upload a document" consists of the same steps as
> you do to upload code; that is, you modify and build source files and then
> you submit your changes via git, which are then reviewed and merged in by a
> committer. The documents are written in asciidoc and follow the
> organization and build structure that already exist in the different
> subdirectories in the docs directory.
>
> I hope this helps,
>
> Gunnar
>
> On Fri, Jul 15, 2016 at 4:09 AM, Yang, Yang (Felix) 
> wrote:
>
> > Hi there，
> > The cwiki link about document submission is horrible. It doesn't show
> > people how to put their 1st article online.  I'm sure there is a button
> > hidden somewhere for doc contributors to upload their article, or to
> create
> > directories, but I just can't find it.
> >
> > Here is what we suggest how the Chinese translations could be submitted ,
> > just to start discussion:
> > Step 1: Shall we set up a new button/tab "中文“（Chinese) on document page,
> > http://trafodion.apache.org/documentation.html, on the blue bar, behind
> > "1.3.0 Release";
> > Please find the "中文" in the enclosed screenshot ("Trafodion Chinese
> > tab.jpg");
> >
> > Step 2:
> > We could give a couple of Chinese contributors write privileges, starting
> > with translations.  Now We have a Chinese wechat group on Trafodion,
> fellow
> > Chinese contributors, please send an email to this list or to
> > yang.y...@esgyn.cn to join the wechat group if you like.
> >
> > Step 3:
> > Upload the translation.  Where is the button? is there an interface like
> > in the attachment "submission page" ?  No, I'm not suggestion submitting
> to
> > cwiki, but just the nice friendly interface to upload like that.
> >
> > To start with, all submissions in Chinese are translations from "Latest"
> > tab only.  The order will be exactly the same.
> >
> > Best,
> > Felix
> >
> >
> > -Original Message-
> > From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> > Sent: Friday, July 15, 2016 3:05 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Chinese Contributor Access
> >
> > Hi,
> >
> > Start here:
> >
> https://cwiki.apache.org/confluence/display/TRAFODION/Modify+Documentation
> >
> > Gunnar
> >
> > On Thu, Jul 14, 2016 at 8:02 AM, Liu, Yu (Yu)  wrote:
> >
> > > Hi all,
> > > Thanks for your suggestion!
> > > We will find a way which serves best.
> > >
> > > Hi Dave & Gunnar,
> > > Currently we have some Chinese guides.
> > > How can we upload/put these files to Apache Trafodion website?
> > >
> > > Many thanks!
> > > Liu Yu
> > >
> > >
> > > -Original Message-
> > > From: Eric Owhadi [mailto:eric.owh...@esgyn.com]
> > > Sent: Thursday, July 14, 2016 9:41 PM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: RE: add a roadmap page in Trafodion's project page
> > >
> > > +1 on this,
> > > Eric
> > >
> > > -Original Message-
> > > From: Liu, Ming (Ming) [mailto:ming@esgyn.cn]
> > > Sent: Thursday, July 14, 2016 8:35 PM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: add a roadmap page in Trafodion's project page
> > >
> > > Hi, all,
> > >
> > > I suggest that Trafodion team should add a 'roadmap' page in the
> > > project's front web page, so users will be clear what to expect in the
> > future.
> > > It will help decision making in some cases.
> > >
> > > Thanks,
> > > Ming
> > >
> > > -Original Message-
> > > From: Jin, Jian (Seth) [mailto:jian@esgyn.cn]
> > > Sent: Thursday, July 14, 2016 12:26 PM
> > > To: dev@trafodion.incubator.apache.org; tapper.gun...@gmail.com
> > > Subject: RE: Chinese Contributor Access
> > >
> > > This would be very user friendly.
> > >
> > > Br,
> > >
> > > Seth
> > >
> > > -Original Message-
> > > From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> > > Sent: 2016年7月13日 23:20
> > > To: dev@trafodion.incubator.apache.org; tapper.gun...@gmail.com
> > > Subject: RE: Chinese Contributor Access
> > >
> > > Hi,
> > >
> > > The two don't conflict.
> > >
> > > The source for documents can be in directories that mirror the English
> > > ones.
> > > Which is a good idea because it will be easier to keep them in synch.
> > >
> > > Links on the web pages and in documents on the other hand can go
> > > transparently across Chinese directories. So to an end-user, it is

Re: [DISCUSS] Apache OpenOffice instead of AsciiDoctor

[Gunnar Tapper]

A lot of copy/paste. :)

Might be able to import the PDFs into OpenOffice, too.



On Fri, Jul 15, 2016 at 10:52 AM, Atanu Mishra 
wrote:

> Hi Gunnar,
>
> All for making things simpler. Which this should.
>
> I assume this means moving away from the asciidoc format. Will there be a
> (big) migration effort?
>
> Thanks,
> Atanu
>
> -Original Message-
> From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> Sent: Friday, July 15, 2016 9:41 AM
> To: dev@trafodion.incubator.apache.org
> Subject: [DISCUSS] Apache OpenOffice instead of AsciiDoctor
>
> Hi,
>
> As you may have seen and/or experienced, it's not easy to work on our
> documentation since you have to setup the build environment, run maven
> builds, etc. And don't get me started on how clumsy it is to update
> documentation.
>
> I propose that we rethink the whole Asciidoctor approach and move to Apache
> OpenOffice instead, which is, of course, open source with a real word
> processor. IMO, the use of Asciidoctor creates a huge barrier to
> documentation creation. It is very, very cumbersome.
>
> In this model, we'd check in the OpenOffice source into the source tree.
> The publication would be a little more manual in that you'd have to
> generate the web pages and PDF files from within OpenOffice but I think
> that's an OK tradeoff. And, we can probably figure out a way to script such
> actions down the line.
>
> Thoughts?
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*
>
>


-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*

RE: [DISCUSS] Apache OpenOffice instead of AsciiDoctor

[Steve Varnau]

Wouldn't the change make it much harder for people to review changes in the
docs?  Github would not give visual diffs.
So every reviewer would have to have openoffice, not just every author.
Even if they have it, pulling the docs and comparing seems like a hard
process.

--Steve

> -Original Message-
> From: Atanu Mishra [mailto:atanumis...@gmail.com]
> Sent: Friday, July 15, 2016 9:52 AM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: [DISCUSS] Apache OpenOffice instead of AsciiDoctor
>
> Hi Gunnar,
>
> All for making things simpler. Which this should.
>
> I assume this means moving away from the asciidoc format. Will there be a
> (big) migration effort?
>
> Thanks,
> Atanu
>
> -Original Message-
> From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> Sent: Friday, July 15, 2016 9:41 AM
> To: dev@trafodion.incubator.apache.org
> Subject: [DISCUSS] Apache OpenOffice instead of AsciiDoctor
>
> Hi,
>
> As you may have seen and/or experienced, it's not easy to work on our
> documentation since you have to setup the build environment, run maven
> builds, etc. And don't get me started on how clumsy it is to update
> documentation.
>
> I propose that we rethink the whole Asciidoctor approach and move to
> Apache
> OpenOffice instead, which is, of course, open source with a real word
> processor. IMO, the use of Asciidoctor creates a huge barrier to
> documentation creation. It is very, very cumbersome.
>
> In this model, we'd check in the OpenOffice source into the source tree.
> The publication would be a little more manual in that you'd have to
> generate the web pages and PDF files from within OpenOffice but I think
> that's an OK tradeoff. And, we can probably figure out a way to script
> such
> actions down the line.
>
> Thoughts?
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*

RE: [DISCUSS] Apache OpenOffice instead of AsciiDoctor

[Atanu Mishra]

Hi Gunnar,

All for making things simpler. Which this should.

I assume this means moving away from the asciidoc format. Will there be a (big) 
migration effort?

Thanks,
Atanu

-Original Message-
From: Gunnar Tapper [mailto:tapper.gun...@gmail.com] 
Sent: Friday, July 15, 2016 9:41 AM
To: dev@trafodion.incubator.apache.org
Subject: [DISCUSS] Apache OpenOffice instead of AsciiDoctor

Hi,

As you may have seen and/or experienced, it's not easy to work on our
documentation since you have to setup the build environment, run maven
builds, etc. And don't get me started on how clumsy it is to update
documentation.

I propose that we rethink the whole Asciidoctor approach and move to Apache
OpenOffice instead, which is, of course, open source with a real word
processor. IMO, the use of Asciidoctor creates a huge barrier to
documentation creation. It is very, very cumbersome.

In this model, we'd check in the OpenOffice source into the source tree.
The publication would be a little more manual in that you'd have to
generate the web pages and PDF files from within OpenOffice but I think
that's an OK tradeoff. And, we can probably figure out a way to script such
actions down the line.

Thoughts?

-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*

[DISCUSS] Apache OpenOffice instead of AsciiDoctor

[Gunnar Tapper]

Hi,

As you may have seen and/or experienced, it's not easy to work on our
documentation since you have to setup the build environment, run maven
builds, etc. And don't get me started on how clumsy it is to update
documentation.

I propose that we rethink the whole Asciidoctor approach and move to Apache
OpenOffice instead, which is, of course, open source with a real word
processor. IMO, the use of Asciidoctor creates a huge barrier to
documentation creation. It is very, very cumbersome.

In this model, we'd check in the OpenOffice source into the source tree.
The publication would be a little more manual in that you'd have to
generate the web pages and PDF files from within OpenOffice but I think
that's an OK tradeoff. And, we can probably figure out a way to script such
actions down the line.

Thoughts?

-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*

RE: Squash commits

[Steve Varnau]

I don't think there is a guaranteed way in git.  It relies on the committer
putting the right info in the commit message.
I think the most important thing is the JIRA ID.

The message might also contain the commit IDs of the squashed branch
commits, but that is harder to recognize, though a search in the log may
find it.

Also if the committer puts in the magic phrase that causes the Apache
automation to close the PR, then the JIRA may also get updated.
Again, relying on care taken by the committer.  I'm not a big fan of
squashed commits because all of this. But it is matter of preference, and
they definitely are useful in certain cases.

Developers & committers, please, please put the JIRA ID in brackets at the
beginning of the line in the PR title and in the merged commit message. And
also at least a couple words that describe the change.  "fix for JIRA 20112"
does not help me a whole lot.
"[TRAFODION-20112] compiler NULL fix"  is not real specific, but gives a
clue and makes sure that the JIRA gets updated with the right PR and commit
info!

Reviewers, please remind developers to update the PR title to the right
format. I see Selva asked someone today. Gold star.

--Steve

> -Original Message-
> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> Sent: Thursday, July 14, 2016 2:25 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Squash commits
>
> Hi,
>
>
>
> One thing I’m noticing about squash commits is that the original pull
> request does not automatically get updated with the SHA of the actual
> merge.
>
>
>
> If one needed to cherry-pick the changes to another branch, is there an
> easy way to discover the proper SHA?
>
>
>
> Thanks,
>
>
>
> Dave

Re: Chinese Contributor Access

[Gunnar Tapper]

Hi Felix,

The documentation is part of the source code. You need to set up a build
environment and use the structure in the docs directory to build/create a
new document.

So, the "click a button to upload a document" consists of the same steps as
you do to upload code; that is, you modify and build source files and then
you submit your changes via git, which are then reviewed and merged in by a
committer. The documents are written in asciidoc and follow the
organization and build structure that already exist in the different
subdirectories in the docs directory.

I hope this helps,

Gunnar

On Fri, Jul 15, 2016 at 4:09 AM, Yang, Yang (Felix) 
wrote:

> Hi there，
> The cwiki link about document submission is horrible. It doesn't show
> people how to put their 1st article online.  I'm sure there is a button
> hidden somewhere for doc contributors to upload their article, or to create
> directories, but I just can't find it.
>
> Here is what we suggest how the Chinese translations could be submitted ,
> just to start discussion:
> Step 1: Shall we set up a new button/tab "中文“（Chinese) on document page,
> http://trafodion.apache.org/documentation.html, on the blue bar, behind
> "1.3.0 Release";
> Please find the "中文" in the enclosed screenshot ("Trafodion Chinese
> tab.jpg");
>
> Step 2:
> We could give a couple of Chinese contributors write privileges, starting
> with translations.  Now We have a Chinese wechat group on Trafodion, fellow
> Chinese contributors, please send an email to this list or to
> yang.y...@esgyn.cn to join the wechat group if you like.
>
> Step 3:
> Upload the translation.  Where is the button? is there an interface like
> in the attachment "submission page" ?  No, I'm not suggestion submitting to
> cwiki, but just the nice friendly interface to upload like that.
>
> To start with, all submissions in Chinese are translations from "Latest"
> tab only.  The order will be exactly the same.
>
> Best,
> Felix
>
>
> -Original Message-
> From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> Sent: Friday, July 15, 2016 3:05 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Chinese Contributor Access
>
> Hi,
>
> Start here:
> https://cwiki.apache.org/confluence/display/TRAFODION/Modify+Documentation
>
> Gunnar
>
> On Thu, Jul 14, 2016 at 8:02 AM, Liu, Yu (Yu)  wrote:
>
> > Hi all,
> > Thanks for your suggestion!
> > We will find a way which serves best.
> >
> > Hi Dave & Gunnar,
> > Currently we have some Chinese guides.
> > How can we upload/put these files to Apache Trafodion website?
> >
> > Many thanks!
> > Liu Yu
> >
> >
> > -Original Message-
> > From: Eric Owhadi [mailto:eric.owh...@esgyn.com]
> > Sent: Thursday, July 14, 2016 9:41 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: add a roadmap page in Trafodion's project page
> >
> > +1 on this,
> > Eric
> >
> > -Original Message-
> > From: Liu, Ming (Ming) [mailto:ming@esgyn.cn]
> > Sent: Thursday, July 14, 2016 8:35 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: add a roadmap page in Trafodion's project page
> >
> > Hi, all,
> >
> > I suggest that Trafodion team should add a 'roadmap' page in the
> > project's front web page, so users will be clear what to expect in the
> future.
> > It will help decision making in some cases.
> >
> > Thanks,
> > Ming
> >
> > -Original Message-
> > From: Jin, Jian (Seth) [mailto:jian@esgyn.cn]
> > Sent: Thursday, July 14, 2016 12:26 PM
> > To: dev@trafodion.incubator.apache.org; tapper.gun...@gmail.com
> > Subject: RE: Chinese Contributor Access
> >
> > This would be very user friendly.
> >
> > Br,
> >
> > Seth
> >
> > -Original Message-
> > From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> > Sent: 2016年7月13日 23:20
> > To: dev@trafodion.incubator.apache.org; tapper.gun...@gmail.com
> > Subject: RE: Chinese Contributor Access
> >
> > Hi,
> >
> > The two don't conflict.
> >
> > The source for documents can be in directories that mirror the English
> > ones.
> > Which is a good idea because it will be easier to keep them in synch.
> >
> > Links on the web pages and in documents on the other hand can go
> > transparently across Chinese directories. So to an end-user, it is
> > just as you describe: Click on the Chinese link on the main web page,
> > then travel to a collection of Chinese pages. Similarly for the
> documents.
> >
> > Dave
> >
> > -Original Message-
> > From: Liu, Yu (Yu) [mailto:yu@esgyn.cn]
> > Sent: Wednesday, July 13, 2016 3:01 AM
> > To: tapper.gun...@gmail.com; dev@trafodion.incubator.apache.org
> > Subject: RE: Chinese Contributor Access
> >
> > Hi Gunnar,
> >
> > Appreciate you taking time to provide your details! I will do more
> > research on them.
> >
> > One question: Why add Chinese directory that corresponds with the
> > English version rather than create a specific section/place?
> >
> > In the latter situation, Chinese (large number of 

Trafodion master Daily Test Result - 270 - Still Failing

[steve . varnau]

Daily Automated Testing master

Jenkins Job:   https://jenkins.esgyn.com/job/Check-Daily-master/270/
Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/270
Bld Downloads: http://traf-builds.esgyn.com

Changes since previous daily build:
[anoop.sharma] JIRA TRAFODION-1843 TRAFODION-2106



Test Job Results:

FAILURE phoenix_part1_T2-cdh (57 min)
FAILURE phoenix_part1_T2-hdp (1 hr 23 min)
FAILURE phoenix_part1_T4-cdh (53 min)
FAILURE phoenix_part1_T4-hdp (1 hr 19 min)
SUCCESS build-master-debug (29 min)
SUCCESS build-master-release (32 min)
SUCCESS core-regress-charsets-cdh (28 min)
SUCCESS core-regress-charsets-hdp (53 min)
SUCCESS core-regress-compGeneral-cdh (42 min)
SUCCESS core-regress-compGeneral-hdp (46 min)
SUCCESS core-regress-core-cdh (51 min)
SUCCESS core-regress-core-hdp (1 hr 16 min)
SUCCESS core-regress-executor-cdh (1 hr 12 min)
SUCCESS core-regress-executor-hdp (1 hr 34 min)
SUCCESS core-regress-fullstack2-cdh (19 min)
SUCCESS core-regress-fullstack2-hdp (28 min)
SUCCESS core-regress-hive-cdh (35 min)
SUCCESS core-regress-hive-hdp (45 min)
SUCCESS core-regress-privs1-cdh (33 min)
SUCCESS core-regress-privs1-hdp (46 min)
SUCCESS core-regress-privs2-cdh (48 min)
SUCCESS core-regress-privs2-hdp (1 hr 2 min)
SUCCESS core-regress-qat-cdh (26 min)
SUCCESS core-regress-qat-hdp (35 min)
SUCCESS core-regress-seabase-cdh (58 min)
SUCCESS core-regress-seabase-hdp (1 hr 23 min)
SUCCESS core-regress-udr-cdh (33 min)
SUCCESS core-regress-udr-hdp (30 min)
SUCCESS jdbc_test-cdh (33 min)
SUCCESS jdbc_test-hdp (37 min)
SUCCESS phoenix_part2_T2-cdh (58 min)
SUCCESS phoenix_part2_T2-hdp (1 hr 18 min)
SUCCESS phoenix_part2_T4-cdh (53 min)
SUCCESS phoenix_part2_T4-hdp (1 hr 17 min)
SUCCESS pyodbc_test-cdh (11 min)
SUCCESS pyodbc_test-hdp (16 min)

RE: Chinese Contributor Access

[Yang, Yang (Felix)]

Hi there， 
The cwiki link about document submission is horrible. It doesn't show people 
how to put their 1st article online.  I'm sure there is a button hidden 
somewhere for doc contributors to upload their article, or to create 
directories, but I just can't find it.

Here is what we suggest how the Chinese translations could be submitted , just 
to start discussion:
Step 1: Shall we set up a new button/tab "中文“（Chinese) on document page, 
http://trafodion.apache.org/documentation.html, on the blue bar, behind "1.3.0 
Release";
Please find the "中文" in the enclosed screenshot ("Trafodion Chinese tab.jpg");

Step 2:
We could give a couple of Chinese contributors write privileges, starting with 
translations.  Now We have a Chinese wechat group on Trafodion, fellow Chinese 
contributors, please send an email to this list or to yang.y...@esgyn.cn to 
join the wechat group if you like. 

Step 3:
Upload the translation.  Where is the button? is there an interface like in the 
attachment "submission page" ?  No, I'm not suggestion submitting to cwiki, but 
just the nice friendly interface to upload like that. 

To start with, all submissions in Chinese are translations from "Latest" tab 
only.  The order will be exactly the same. 

Best, 
Felix


-Original Message-
From: Gunnar Tapper [mailto:tapper.gun...@gmail.com] 
Sent: Friday, July 15, 2016 3:05 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: Chinese Contributor Access

Hi,

Start here:
https://cwiki.apache.org/confluence/display/TRAFODION/Modify+Documentation

Gunnar

On Thu, Jul 14, 2016 at 8:02 AM, Liu, Yu (Yu)  wrote:

> Hi all,
> Thanks for your suggestion!
> We will find a way which serves best.
>
> Hi Dave & Gunnar,
> Currently we have some Chinese guides.
> How can we upload/put these files to Apache Trafodion website?
>
> Many thanks!
> Liu Yu
>
>
> -Original Message-
> From: Eric Owhadi [mailto:eric.owh...@esgyn.com]
> Sent: Thursday, July 14, 2016 9:41 PM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: add a roadmap page in Trafodion's project page
>
> +1 on this,
> Eric
>
> -Original Message-
> From: Liu, Ming (Ming) [mailto:ming@esgyn.cn]
> Sent: Thursday, July 14, 2016 8:35 PM
> To: dev@trafodion.incubator.apache.org
> Subject: add a roadmap page in Trafodion's project page
>
> Hi, all,
>
> I suggest that Trafodion team should add a 'roadmap' page in the 
> project's front web page, so users will be clear what to expect in the future.
> It will help decision making in some cases.
>
> Thanks,
> Ming
>
> -Original Message-
> From: Jin, Jian (Seth) [mailto:jian@esgyn.cn]
> Sent: Thursday, July 14, 2016 12:26 PM
> To: dev@trafodion.incubator.apache.org; tapper.gun...@gmail.com
> Subject: RE: Chinese Contributor Access
>
> This would be very user friendly.
>
> Br,
>
> Seth
>
> -Original Message-
> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> Sent: 2016年7月13日 23:20
> To: dev@trafodion.incubator.apache.org; tapper.gun...@gmail.com
> Subject: RE: Chinese Contributor Access
>
> Hi,
>
> The two don't conflict.
>
> The source for documents can be in directories that mirror the English 
> ones.
> Which is a good idea because it will be easier to keep them in synch.
>
> Links on the web pages and in documents on the other hand can go 
> transparently across Chinese directories. So to an end-user, it is 
> just as you describe: Click on the Chinese link on the main web page, 
> then travel to a collection of Chinese pages. Similarly for the documents.
>
> Dave
>
> -Original Message-
> From: Liu, Yu (Yu) [mailto:yu@esgyn.cn]
> Sent: Wednesday, July 13, 2016 3:01 AM
> To: tapper.gun...@gmail.com; dev@trafodion.incubator.apache.org
> Subject: RE: Chinese Contributor Access
>
> Hi Gunnar,
>
> Appreciate you taking time to provide your details! I will do more 
> research on them.
>
> One question: Why add Chinese directory that corresponds with the 
> English version rather than create a specific section/place?
>
> In the latter situation, Chinese (large number of users) could locate 
> their desired information with fastest and fewest clicks, the user 
> experience & user usability will be improved significantly, 
> consequently it will contribute to the promotion of Apache Trafodion website 
> as well.
>
> Thanks!
> Liu Yu
>
>
> -Original Message-
> From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> Sent: Wednesday, July 13, 2016 11:26 AM
> To: dev@trafodion.incubator.apache.org
> Cc: Dave Birdsall ; Jin, Jian (Seth) < 
> jian@esgyn.cn>; Yang, Yang (Felix) 
> Subject: Re: Chinese Contributor Access
>
> Hi,
>
> It's definitely a good idea to add a set of Chinese-language pages and 
> user guides. Most of the documentation and web pages are located under 
> the docs/ directory. I propose that we keep this simple: simply add a 
> [document]_cn directory that corresponds with the English version. For 

trafodion-2016

[Ma, Sheng-Chen (Aven)]

Hi all:
Is there some one can review #568 ? it's a long time.

https://github.com/apache/incubator-trafodion/pull/568

thanks