Re: [RELEASE PLANNING] 2.1 Release Management

[Gunnar Tapper]

Thanks Selva. What are the Jira numbers for these changes?

It seems to me that the configuration file needs to be documented. If not,
how would anyone know how to use it?

Gunnar

On Thu, Dec 1, 2016 at 7:56 AM, Selva Govindarajan <
selva.govindara...@esgyn.com> wrote:

> Hi Gunnar,
>
>
> I have introduced trafodion to have its own configuration file similar to
> hbase-site.xml. This file can contain trafodion specific configuration
> (Trafodion doesn't have anything as of now) or hbase configuration
> parameters that will take effect for trafodion client processes only.
>
>
> I have also streamlined the SQL/TM component to return error message fully
> to end user whenever possible. So,  when a SQL command returns an error,
> there are cases the end user will not see the whole stack of error
> sequence. He/She needs to go through the different logs to identify the
> source of the issue.
>
>
> If this needs to be documented, you can add to the list. I will take up
> the action items to document it. I am unable to edit the document.
>
>
> Selva
>
> .
>
>
>
> Selva
>
>
> 
> From: Gunnar Tapper 
> Sent: Thursday, December 1, 2016 6:28 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: [RELEASE PLANNING] 2.1 Release Management
>
> Thanks Ming. For tests, I think it's very jira specific. 1673 is about
> syntax and, therefore, is a matter of richness in the regression test case.
>
> However, I'm wondering of bigger-ticket items such as odb Windows, CentOS
> 7, etc. It seems to me that we need a little more testing for such items if
> they are part of the release?
>
> Gunnar
>
> On Wed, Nov 30, 2016 at 7:51 PM, Liu, Ming (Ming) 
> wrote:
>
> > Hi, Gunnar,
> > For testing, for example, I was working for JIRA 1673, and added
> > regression test cases for this feature. I assume this will be good.
> > For documentation, as we discussed once before, a good practice will be
> > the author of the feature to update required document as well.
> > I will update doc for some new features covered by the JIRA I owned. Will
> > file new JIRAs to track on and mark the target release as R2.1
> >
> > thanks,
> > Ming
> >
> > -Original Message-
> > From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> > Sent: Thursday, December 01, 2016 9:33 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: [RELEASE PLANNING] 2.1 Release Management
> >
> > Hi,
> >
> > I've created a page sub tree for release management on the Trafodion
> wiki.
> > The idea is to provide a poor person's self-service release planning and
> > status tool.
> >
> > Please refer to
> > https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.1 for
> the
> > 2.1 release management information.
> >
> > As you can see, we've identified nine Jiras as release drivers. I'm not
> > sure whether the Jiras in Open state are actively worked on and/or will
> > make the 2.1 release.
> >
> > I expect that release drivers will have specific testing and that we'll
> > need to update the documentation for each release driver. Perusing the
> > Jiras, I saw no indication of planned test or planned documentation
> > updates?
> >
> > Let's pick on Jira 1673 as an example. What testing is being planned and
> > who's doing it? What changes are needed to the SQL Reference Guide and
> > who's doing it?
> >
> > I'm going to build out the Release Checklist part and look for other
> > documentation jiras.
> >
> > Meanwhile, I'm expecting whomever that is responsible for a release
> driver
> > jira to ensure that we have end-to-end delivery of the function. Please
> > edit the wiki page directly even if you're just opening a new jira to
> > document the feature.
> >
> > Also, if you disagree with a release driver or think a new release driver
> > should be added, then please start a discussion on the dev list.
> >
> >
> > --
> > 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.*
>



-- 
Thanks,

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

Re: Can't edit wiki

[Gunnar Tapper]

The issue was that I had not changed my e-mail address away from my
previous employer. 1.5 years later, it became a problem for some reason.

On Wed, Nov 30, 2016 at 7:29 PM, Jin, Jian (Seth)  wrote:

> Yes, this should be bug, once someone forgets password and will never
> reset/find again
>
> Br,
>
> Seth
>
> -Original Message-
> From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> Sent: 2016年12月1日 2:40
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Can't edit wiki
>
> Which will not allow me to login or redo the password. Weird. I'll contact
> infrastructure.
>
> Thanks,
>
> Gunnar
>
> On Wed, Nov 30, 2016 at 11:34 AM, Dave Birdsall 
> wrote:
>
> > I just looked at the wiki Permissions page. It shows that you have
> > editing rights under the ID "gtapper".
> >
> > -Original Message-
> > From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> > Sent: Wednesday, November 30, 2016 10:31 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Can't edit wiki
> >
> > Can someone check why I can't edit the Trafodion wiki all of a sudden?
> >
> > --
> > 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.*
>



-- 
Thanks,

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

Re: [RELEASE PLANNING] 2.1 Release Management

[Gunnar Tapper]

Thanks Ming. For tests, I think it's very jira specific. 1673 is about
syntax and, therefore, is a matter of richness in the regression test case.

However, I'm wondering of bigger-ticket items such as odb Windows, CentOS
7, etc. It seems to me that we need a little more testing for such items if
they are part of the release?

Gunnar

On Wed, Nov 30, 2016 at 7:51 PM, Liu, Ming (Ming)  wrote:

> Hi, Gunnar,
> For testing, for example, I was working for JIRA 1673, and added
> regression test cases for this feature. I assume this will be good.
> For documentation, as we discussed once before, a good practice will be
> the author of the feature to update required document as well.
> I will update doc for some new features covered by the JIRA I owned. Will
> file new JIRAs to track on and mark the target release as R2.1
>
> thanks,
> Ming
>
> -Original Message-
> From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> Sent: Thursday, December 01, 2016 9:33 AM
> To: dev@trafodion.incubator.apache.org
> Subject: [RELEASE PLANNING] 2.1 Release Management
>
> Hi,
>
> I've created a page sub tree for release management on the Trafodion wiki.
> The idea is to provide a poor person's self-service release planning and
> status tool.
>
> Please refer to
> https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.1 for the
> 2.1 release management information.
>
> As you can see, we've identified nine Jiras as release drivers. I'm not
> sure whether the Jiras in Open state are actively worked on and/or will
> make the 2.1 release.
>
> I expect that release drivers will have specific testing and that we'll
> need to update the documentation for each release driver. Perusing the
> Jiras, I saw no indication of planned test or planned documentation
> updates?
>
> Let's pick on Jira 1673 as an example. What testing is being planned and
> who's doing it? What changes are needed to the SQL Reference Guide and
> who's doing it?
>
> I'm going to build out the Release Checklist part and look for other
> documentation jiras.
>
> Meanwhile, I'm expecting whomever that is responsible for a release driver
> jira to ensure that we have end-to-end delivery of the function. Please
> edit the wiki page directly even if you're just opening a new jira to
> document the feature.
>
> Also, if you disagree with a release driver or think a new release driver
> should be added, then please start a discussion on the dev list.
>
>
> --
> 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.*