You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Prasanna Santhanam <pr...@citrix.com> on 2012/12/19 00:11:35 UTC
Re: Request for cloudstack-qa mailing list and QA Scrum call
On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > Hi All,
> >
> > Reaching out to community to see if we can have a dedicated QA
> > mailing list mainly to have a focused attention around QA
> > Activities.
> >
> >
> > - To discuss automation acceleration. We already have
> > sizable scripts and need to get those running in to apache env
> >
> > - Discuss QA strategy and have community participate little
> > bit more - Dev community is very active but QA is not at the same
> > level. There are too many discussions in dev mailing list already.
> > Afraid that QA may not get enough attention
> >
> > - Discuss project QA activities and track progress and
> > present relevant info to community. Intention is not to take away
> > visibility but to have a focused vision on QA.
> >
> > - Discuss other QA initiatives and have owners drive these
> > initiatives - mainly around automation frameworks, tools
> > implementation for QA
> >
> >
> > Please do express your opinion on this.
> >
> > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > activities starting next week as we are getting close to the
> > release.
> >
>
> Why not use the -users list? It's not high-traffic and QA are users
> testing/using the product? It will encourage our users to test
> alongside releases and participate in the testing process. Some of our
> users I'm sure can contribute automated tests.
>
Including the users (+cross-posting)
--
Prasanna.,
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi
On Wed, Dec 19, 2012 at 1:02 AM, Sudha Ponnaganti <
sudha.ponnaganti@citrix.com> wrote:
> Thanks for clarification Mohammad Nour! I do not necessarily disagree
> with what you are suggesting but from what we have seen in 4.0 and 4.0.1,
> it did not work much for testing activity /QA. May have worked if project
> is smaller. But Cloudstack is not smaller anymore and as mentioned earlier
> the discussions have grown in other development areas but not seeing same
> growth in qa aspect. So trying to find ways to provide a focused attention
> and of course it will not be isolated group as it is open just like user or
> dev lists.
>
> It looks like this approach worked for some bigger open source projects -
> https://quality.mozilla.org/ ( there are multiple mailing lists even
> within QA)
>
This is really interesting, although the example does not apply here as it
looks like a specialized QA community thing AFAIU
>
> However for starters, we can discuss with QA prefix and see how it goes.
>
+1 I would go that way and if it proves that the traffic is really high to
the point that it spams the -dev list itself then at that time we have a
real reason to go with to INFRA
>
> -----Original Message-----
> From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
> Sent: Tuesday, December 18, 2012 3:40 PM
> To: CloudStack Users
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> Hi Sudha...
>
>
> On Wed, Dec 19, 2012 at 12:28 AM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
> > One of the concerns is that QA may not feel comfortable to discuss all
> > the QA topics in Dev mailing list.
> > Would like to attract QA community to contribute more than just
> > testing - development of tools and adoption of automation.
> >
> > As is QA is not participating frequently and current dedicated effort
> > is to accelerate that. I am not sure if that would be successful or
> > not but I sense that QA is not feeling comfortable to discuss QA
> > topics in Dev mailing lists. Several times QA folks are being nudged
> > to post on dev mailing lists from few folks participated in 4.0 QA
> > effort. That is why I thought this approach might help.
> >
> > Intention is not to isolate this mailing list but to keep focus and
> > encourage participation.
> >
>
> I understand your concern, but allow me to disagree with you about one
> main point, IMO this is encouraging more to like divide the ACS community,
> using different mailing lists is not to categorize people or to use it as
> as if we have departments in team, we use different mailing lists mainly
> for better scope and some times for privacy when it matters about some
> aspects that should not be discussed in public and in this case I don't see
> any of these, I know you don't mean that at all I am just explaining what
> would that lead at the end
>
> Actually I would not call the QA ppl, I will call them contributors, or
> persons interested to contribute to ACS development related tasks which are
> of more QA nature
>
> Actually I would better encourage them to go one the -dev list and start
> spamming it with QA e-mails :D
>
>
> >
> >
> >
> > -----Original Message-----
> > From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
> > Sent: Tuesday, December 18, 2012 3:17 PM
> > To: cloudstack-dev@incubator.apache.org; CloudStack Users
> > Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
> >
> > Hi
> >
> > Allow me to dis-agree with you about one minor point that
> > differentiates frequest/planned/scheduled QA tasks or activities than
> > than what users find while using ACS, I think what is proposed is
> > related to the former point
> >
> > The idea itself is appealing but the amount of interaction really
> > needs separate mailing list ? Can we just send e-mail tagged with [QA]
> > for example which then helps filter out QA related e-mails ?
> >
> >
> > On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
> > prasanna.santhanam@citrix.com> wrote:
> >
> > > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > > Hi All,
> > > > >
> > > > > Reaching out to community to see if we can have a dedicated QA
> > > > > mailing list mainly to have a focused attention around QA
> > > > > Activities.
> > > > >
> > > > >
> > > > > - To discuss automation acceleration. We already have
> > > > > sizable scripts and need to get those running in to apache env
> > > > >
> > > > > - Discuss QA strategy and have community participate
> little
> > > > > bit more - Dev community is very active but QA is not at the
> > > > > same level. There are too many discussions in dev mailing list
> already.
> > > > > Afraid that QA may not get enough attention
> > > > >
> > > > > - Discuss project QA activities and track progress and
> > > > > present relevant info to community. Intention is not to take
> > > > > away visibility but to have a focused vision on QA.
> > > > >
> > > > > - Discuss other QA initiatives and have owners drive these
> > > > > initiatives - mainly around automation frameworks, tools
> > > > > implementation for QA
> > > > >
> > > > >
> > > > > Please do express your opinion on this.
> > > > >
> > > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > > activities starting next week as we are getting close to the
> > > > > release.
> > > > >
> > > >
> > > > Why not use the -users list? It's not high-traffic and QA are
> > > > users testing/using the product? It will encourage our users to
> > > > test alongside releases and participate in the testing process.
> > > > Some of our users I'm sure can contribute automated tests.
> > > >
> > > Including the users (+cross-posting)
> > >
> > >
> > > --
> > > Prasanna.,
> > >
> >
> >
> >
> > --
> > Thanks
> > - Mohammad Nour
> > ----
> > "Life is like riding a bicycle. To keep your balance you must keep
> moving"
> > - Albert Einstein
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
RE: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Sudha Ponnaganti <su...@citrix.com>.
Thanks for clarification Mohammad Nour! I do not necessarily disagree with what you are suggesting but from what we have seen in 4.0 and 4.0.1, it did not work much for testing activity /QA. May have worked if project is smaller. But Cloudstack is not smaller anymore and as mentioned earlier the discussions have grown in other development areas but not seeing same growth in qa aspect. So trying to find ways to provide a focused attention and of course it will not be isolated group as it is open just like user or dev lists.
It looks like this approach worked for some bigger open source projects - https://quality.mozilla.org/ ( there are multiple mailing lists even within QA)
However for starters, we can discuss with QA prefix and see how it goes.
-----Original Message-----
From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
Sent: Tuesday, December 18, 2012 3:40 PM
To: CloudStack Users
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
Hi Sudha...
On Wed, Dec 19, 2012 at 12:28 AM, Sudha Ponnaganti < sudha.ponnaganti@citrix.com> wrote:
> One of the concerns is that QA may not feel comfortable to discuss all
> the QA topics in Dev mailing list.
> Would like to attract QA community to contribute more than just
> testing - development of tools and adoption of automation.
>
> As is QA is not participating frequently and current dedicated effort
> is to accelerate that. I am not sure if that would be successful or
> not but I sense that QA is not feeling comfortable to discuss QA
> topics in Dev mailing lists. Several times QA folks are being nudged
> to post on dev mailing lists from few folks participated in 4.0 QA
> effort. That is why I thought this approach might help.
>
> Intention is not to isolate this mailing list but to keep focus and
> encourage participation.
>
I understand your concern, but allow me to disagree with you about one main point, IMO this is encouraging more to like divide the ACS community, using different mailing lists is not to categorize people or to use it as as if we have departments in team, we use different mailing lists mainly for better scope and some times for privacy when it matters about some aspects that should not be discussed in public and in this case I don't see any of these, I know you don't mean that at all I am just explaining what would that lead at the end
Actually I would not call the QA ppl, I will call them contributors, or persons interested to contribute to ACS development related tasks which are of more QA nature
Actually I would better encourage them to go one the -dev list and start spamming it with QA e-mails :D
>
>
>
> -----Original Message-----
> From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
> Sent: Tuesday, December 18, 2012 3:17 PM
> To: cloudstack-dev@incubator.apache.org; CloudStack Users
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> Hi
>
> Allow me to dis-agree with you about one minor point that
> differentiates frequest/planned/scheduled QA tasks or activities than
> than what users find while using ACS, I think what is proposed is
> related to the former point
>
> The idea itself is appealing but the amount of interaction really
> needs separate mailing list ? Can we just send e-mail tagged with [QA]
> for example which then helps filter out QA related e-mails ?
>
>
> On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
> prasanna.santhanam@citrix.com> wrote:
>
> > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > Hi All,
> > > >
> > > > Reaching out to community to see if we can have a dedicated QA
> > > > mailing list mainly to have a focused attention around QA
> > > > Activities.
> > > >
> > > >
> > > > - To discuss automation acceleration. We already have
> > > > sizable scripts and need to get those running in to apache env
> > > >
> > > > - Discuss QA strategy and have community participate little
> > > > bit more - Dev community is very active but QA is not at the
> > > > same level. There are too many discussions in dev mailing list already.
> > > > Afraid that QA may not get enough attention
> > > >
> > > > - Discuss project QA activities and track progress and
> > > > present relevant info to community. Intention is not to take
> > > > away visibility but to have a focused vision on QA.
> > > >
> > > > - Discuss other QA initiatives and have owners drive these
> > > > initiatives - mainly around automation frameworks, tools
> > > > implementation for QA
> > > >
> > > >
> > > > Please do express your opinion on this.
> > > >
> > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > activities starting next week as we are getting close to the
> > > > release.
> > > >
> > >
> > > Why not use the -users list? It's not high-traffic and QA are
> > > users testing/using the product? It will encourage our users to
> > > test alongside releases and participate in the testing process.
> > > Some of our users I'm sure can contribute automated tests.
> > >
> > Including the users (+cross-posting)
> >
> >
> > --
> > Prasanna.,
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
RE: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Sudha Ponnaganti <su...@citrix.com>.
Thanks for clarification Mohammad Nour! I do not necessarily disagree with what you are suggesting but from what we have seen in 4.0 and 4.0.1, it did not work much for testing activity /QA. May have worked if project is smaller. But Cloudstack is not smaller anymore and as mentioned earlier the discussions have grown in other development areas but not seeing same growth in qa aspect. So trying to find ways to provide a focused attention and of course it will not be isolated group as it is open just like user or dev lists.
It looks like this approach worked for some bigger open source projects - https://quality.mozilla.org/ ( there are multiple mailing lists even within QA)
However for starters, we can discuss with QA prefix and see how it goes.
-----Original Message-----
From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
Sent: Tuesday, December 18, 2012 3:40 PM
To: CloudStack Users
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
Hi Sudha...
On Wed, Dec 19, 2012 at 12:28 AM, Sudha Ponnaganti < sudha.ponnaganti@citrix.com> wrote:
> One of the concerns is that QA may not feel comfortable to discuss all
> the QA topics in Dev mailing list.
> Would like to attract QA community to contribute more than just
> testing - development of tools and adoption of automation.
>
> As is QA is not participating frequently and current dedicated effort
> is to accelerate that. I am not sure if that would be successful or
> not but I sense that QA is not feeling comfortable to discuss QA
> topics in Dev mailing lists. Several times QA folks are being nudged
> to post on dev mailing lists from few folks participated in 4.0 QA
> effort. That is why I thought this approach might help.
>
> Intention is not to isolate this mailing list but to keep focus and
> encourage participation.
>
I understand your concern, but allow me to disagree with you about one main point, IMO this is encouraging more to like divide the ACS community, using different mailing lists is not to categorize people or to use it as as if we have departments in team, we use different mailing lists mainly for better scope and some times for privacy when it matters about some aspects that should not be discussed in public and in this case I don't see any of these, I know you don't mean that at all I am just explaining what would that lead at the end
Actually I would not call the QA ppl, I will call them contributors, or persons interested to contribute to ACS development related tasks which are of more QA nature
Actually I would better encourage them to go one the -dev list and start spamming it with QA e-mails :D
>
>
>
> -----Original Message-----
> From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
> Sent: Tuesday, December 18, 2012 3:17 PM
> To: cloudstack-dev@incubator.apache.org; CloudStack Users
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> Hi
>
> Allow me to dis-agree with you about one minor point that
> differentiates frequest/planned/scheduled QA tasks or activities than
> than what users find while using ACS, I think what is proposed is
> related to the former point
>
> The idea itself is appealing but the amount of interaction really
> needs separate mailing list ? Can we just send e-mail tagged with [QA]
> for example which then helps filter out QA related e-mails ?
>
>
> On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
> prasanna.santhanam@citrix.com> wrote:
>
> > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > Hi All,
> > > >
> > > > Reaching out to community to see if we can have a dedicated QA
> > > > mailing list mainly to have a focused attention around QA
> > > > Activities.
> > > >
> > > >
> > > > - To discuss automation acceleration. We already have
> > > > sizable scripts and need to get those running in to apache env
> > > >
> > > > - Discuss QA strategy and have community participate little
> > > > bit more - Dev community is very active but QA is not at the
> > > > same level. There are too many discussions in dev mailing list already.
> > > > Afraid that QA may not get enough attention
> > > >
> > > > - Discuss project QA activities and track progress and
> > > > present relevant info to community. Intention is not to take
> > > > away visibility but to have a focused vision on QA.
> > > >
> > > > - Discuss other QA initiatives and have owners drive these
> > > > initiatives - mainly around automation frameworks, tools
> > > > implementation for QA
> > > >
> > > >
> > > > Please do express your opinion on this.
> > > >
> > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > activities starting next week as we are getting close to the
> > > > release.
> > > >
> > >
> > > Why not use the -users list? It's not high-traffic and QA are
> > > users testing/using the product? It will encourage our users to
> > > test alongside releases and participate in the testing process.
> > > Some of our users I'm sure can contribute automated tests.
> > >
> > Including the users (+cross-posting)
> >
> >
> > --
> > Prasanna.,
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Sudha...
On Wed, Dec 19, 2012 at 12:28 AM, Sudha Ponnaganti <
sudha.ponnaganti@citrix.com> wrote:
> One of the concerns is that QA may not feel comfortable to discuss all the
> QA topics in Dev mailing list.
> Would like to attract QA community to contribute more than just testing -
> development of tools and adoption of automation.
>
> As is QA is not participating frequently and current dedicated effort is
> to accelerate that. I am not sure if that would be successful or not but I
> sense that QA is not feeling comfortable to discuss QA topics in Dev
> mailing lists. Several times QA folks are being nudged to post on dev
> mailing lists from few folks participated in 4.0 QA effort. That is why I
> thought this approach might help.
>
> Intention is not to isolate this mailing list but to keep focus and
> encourage participation.
>
I understand your concern, but allow me to disagree with you about one main
point, IMO this is encouraging more to like divide the ACS community, using
different mailing lists is not to categorize people or to use it as as if
we have departments in team, we use different mailing lists mainly for
better scope and some times for privacy when it matters about some aspects
that should not be discussed in public and in this case I don't see any of
these, I know you don't mean that at all I am just explaining what would
that lead at the end
Actually I would not call the QA ppl, I will call them contributors, or
persons interested to contribute to ACS development related tasks which are
of more QA nature
Actually I would better encourage them to go one the -dev list and start
spamming it with QA e-mails :D
>
>
>
> -----Original Message-----
> From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
> Sent: Tuesday, December 18, 2012 3:17 PM
> To: cloudstack-dev@incubator.apache.org; CloudStack Users
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> Hi
>
> Allow me to dis-agree with you about one minor point that
> differentiates frequest/planned/scheduled QA tasks or activities than than
> what users find while using ACS, I think what is proposed is related to the
> former point
>
> The idea itself is appealing but the amount of interaction really needs
> separate mailing list ? Can we just send e-mail tagged with [QA] for
> example which then helps filter out QA related e-mails ?
>
>
> On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
> prasanna.santhanam@citrix.com> wrote:
>
> > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > Hi All,
> > > >
> > > > Reaching out to community to see if we can have a dedicated QA
> > > > mailing list mainly to have a focused attention around QA
> > > > Activities.
> > > >
> > > >
> > > > - To discuss automation acceleration. We already have
> > > > sizable scripts and need to get those running in to apache env
> > > >
> > > > - Discuss QA strategy and have community participate little
> > > > bit more - Dev community is very active but QA is not at the same
> > > > level. There are too many discussions in dev mailing list already.
> > > > Afraid that QA may not get enough attention
> > > >
> > > > - Discuss project QA activities and track progress and
> > > > present relevant info to community. Intention is not to take away
> > > > visibility but to have a focused vision on QA.
> > > >
> > > > - Discuss other QA initiatives and have owners drive these
> > > > initiatives - mainly around automation frameworks, tools
> > > > implementation for QA
> > > >
> > > >
> > > > Please do express your opinion on this.
> > > >
> > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > activities starting next week as we are getting close to the
> > > > release.
> > > >
> > >
> > > Why not use the -users list? It's not high-traffic and QA are users
> > > testing/using the product? It will encourage our users to test
> > > alongside releases and participate in the testing process. Some of
> > > our users I'm sure can contribute automated tests.
> > >
> > Including the users (+cross-posting)
> >
> >
> > --
> > Prasanna.,
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Sudha...
On Wed, Dec 19, 2012 at 12:28 AM, Sudha Ponnaganti <
sudha.ponnaganti@citrix.com> wrote:
> One of the concerns is that QA may not feel comfortable to discuss all the
> QA topics in Dev mailing list.
> Would like to attract QA community to contribute more than just testing -
> development of tools and adoption of automation.
>
> As is QA is not participating frequently and current dedicated effort is
> to accelerate that. I am not sure if that would be successful or not but I
> sense that QA is not feeling comfortable to discuss QA topics in Dev
> mailing lists. Several times QA folks are being nudged to post on dev
> mailing lists from few folks participated in 4.0 QA effort. That is why I
> thought this approach might help.
>
> Intention is not to isolate this mailing list but to keep focus and
> encourage participation.
>
I understand your concern, but allow me to disagree with you about one main
point, IMO this is encouraging more to like divide the ACS community, using
different mailing lists is not to categorize people or to use it as as if
we have departments in team, we use different mailing lists mainly for
better scope and some times for privacy when it matters about some aspects
that should not be discussed in public and in this case I don't see any of
these, I know you don't mean that at all I am just explaining what would
that lead at the end
Actually I would not call the QA ppl, I will call them contributors, or
persons interested to contribute to ACS development related tasks which are
of more QA nature
Actually I would better encourage them to go one the -dev list and start
spamming it with QA e-mails :D
>
>
>
> -----Original Message-----
> From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
> Sent: Tuesday, December 18, 2012 3:17 PM
> To: cloudstack-dev@incubator.apache.org; CloudStack Users
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> Hi
>
> Allow me to dis-agree with you about one minor point that
> differentiates frequest/planned/scheduled QA tasks or activities than than
> what users find while using ACS, I think what is proposed is related to the
> former point
>
> The idea itself is appealing but the amount of interaction really needs
> separate mailing list ? Can we just send e-mail tagged with [QA] for
> example which then helps filter out QA related e-mails ?
>
>
> On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
> prasanna.santhanam@citrix.com> wrote:
>
> > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > Hi All,
> > > >
> > > > Reaching out to community to see if we can have a dedicated QA
> > > > mailing list mainly to have a focused attention around QA
> > > > Activities.
> > > >
> > > >
> > > > - To discuss automation acceleration. We already have
> > > > sizable scripts and need to get those running in to apache env
> > > >
> > > > - Discuss QA strategy and have community participate little
> > > > bit more - Dev community is very active but QA is not at the same
> > > > level. There are too many discussions in dev mailing list already.
> > > > Afraid that QA may not get enough attention
> > > >
> > > > - Discuss project QA activities and track progress and
> > > > present relevant info to community. Intention is not to take away
> > > > visibility but to have a focused vision on QA.
> > > >
> > > > - Discuss other QA initiatives and have owners drive these
> > > > initiatives - mainly around automation frameworks, tools
> > > > implementation for QA
> > > >
> > > >
> > > > Please do express your opinion on this.
> > > >
> > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > activities starting next week as we are getting close to the
> > > > release.
> > > >
> > >
> > > Why not use the -users list? It's not high-traffic and QA are users
> > > testing/using the product? It will encourage our users to test
> > > alongside releases and participate in the testing process. Some of
> > > our users I'm sure can contribute automated tests.
> > >
> > Including the users (+cross-posting)
> >
> >
> > --
> > Prasanna.,
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Prasanna Santhanam <pr...@citrix.com>.
On Wed, Dec 19, 2012 at 04:58:35AM +0530, Sudha Ponnaganti wrote:
> One of the concerns is that QA may not feel comfortable to discuss
> all the QA topics in Dev mailing list.
> Would like to attract QA community to contribute more than just
> testing - development of tools and adoption of automation.
>
> As is QA is not participating frequently and current dedicated
> effort is to accelerate that. I am not sure if that would be
> successful or not but I sense that QA is not feeling comfortable to
> discuss QA topics in Dev mailing lists. Several times QA folks are
> being nudged to post on dev mailing lists from few folks
> participated in 4.0 QA effort. That is why I thought this approach
> might help.
All folks should be welcome and feel comfortable mailing the lists.
I think a tag [QA] marking testing concerns can simplify the process
for devs who might not be interested in following up on the topic.
IMO right now the difficulty is in rounding up folks for a test
process that works asynchronously across timezones. As a test
contributor I don't see a clear QA process which makes it confusing
for me to begin.
Some of the difficulties can be that:
QA requires sufficient HW to test some of this stuff. Ilya is one
person I've seen come forward to test features proposed. Which is why
I suggest the users lists. But I see Alex's point about nightly
builds. That can be simplified too IMO with tags on the email. But if
discussions can be kept in -dev and developers don't mind, I'm all for
it as well.
QA can in fact participate in reviewing features that are being
proposed on dev lists. They are good judges of the feature and its
requirement and how it fits in to the stack.
There are also various kinds of test groups which we don't quite
recognize. All of them help us with the QA of the stack:
Test groups can be:
1. unittest writers
2. feature reviewers
3. automated integration tests
4. Doc bug and review
5. Those verifying bugs raised in release cycles.
6. CI and infra
Would be really nice to see all the folks come together and figure out
how to unite the QA effort.
--
Prasanna.,
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Prasanna Santhanam <pr...@citrix.com>.
On Wed, Dec 19, 2012 at 04:58:35AM +0530, Sudha Ponnaganti wrote:
> One of the concerns is that QA may not feel comfortable to discuss
> all the QA topics in Dev mailing list.
> Would like to attract QA community to contribute more than just
> testing - development of tools and adoption of automation.
>
> As is QA is not participating frequently and current dedicated
> effort is to accelerate that. I am not sure if that would be
> successful or not but I sense that QA is not feeling comfortable to
> discuss QA topics in Dev mailing lists. Several times QA folks are
> being nudged to post on dev mailing lists from few folks
> participated in 4.0 QA effort. That is why I thought this approach
> might help.
All folks should be welcome and feel comfortable mailing the lists.
I think a tag [QA] marking testing concerns can simplify the process
for devs who might not be interested in following up on the topic.
IMO right now the difficulty is in rounding up folks for a test
process that works asynchronously across timezones. As a test
contributor I don't see a clear QA process which makes it confusing
for me to begin.
Some of the difficulties can be that:
QA requires sufficient HW to test some of this stuff. Ilya is one
person I've seen come forward to test features proposed. Which is why
I suggest the users lists. But I see Alex's point about nightly
builds. That can be simplified too IMO with tags on the email. But if
discussions can be kept in -dev and developers don't mind, I'm all for
it as well.
QA can in fact participate in reviewing features that are being
proposed on dev lists. They are good judges of the feature and its
requirement and how it fits in to the stack.
There are also various kinds of test groups which we don't quite
recognize. All of them help us with the QA of the stack:
Test groups can be:
1. unittest writers
2. feature reviewers
3. automated integration tests
4. Doc bug and review
5. Those verifying bugs raised in release cycles.
6. CI and infra
Would be really nice to see all the folks come together and figure out
how to unite the QA effort.
--
Prasanna.,
RE: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Sudha Ponnaganti <su...@citrix.com>.
One of the concerns is that QA may not feel comfortable to discuss all the QA topics in Dev mailing list.
Would like to attract QA community to contribute more than just testing - development of tools and adoption of automation.
As is QA is not participating frequently and current dedicated effort is to accelerate that. I am not sure if that would be successful or not but I sense that QA is not feeling comfortable to discuss QA topics in Dev mailing lists. Several times QA folks are being nudged to post on dev mailing lists from few folks participated in 4.0 QA effort. That is why I thought this approach might help.
Intention is not to isolate this mailing list but to keep focus and encourage participation.
-----Original Message-----
From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
Sent: Tuesday, December 18, 2012 3:17 PM
To: cloudstack-dev@incubator.apache.org; CloudStack Users
Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
Hi
Allow me to dis-agree with you about one minor point that differentiates frequest/planned/scheduled QA tasks or activities than than what users find while using ACS, I think what is proposed is related to the former point
The idea itself is appealing but the amount of interaction really needs separate mailing list ? Can we just send e-mail tagged with [QA] for example which then helps filter out QA related e-mails ?
On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam < prasanna.santhanam@citrix.com> wrote:
> On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > Hi All,
> > >
> > > Reaching out to community to see if we can have a dedicated QA
> > > mailing list mainly to have a focused attention around QA
> > > Activities.
> > >
> > >
> > > - To discuss automation acceleration. We already have
> > > sizable scripts and need to get those running in to apache env
> > >
> > > - Discuss QA strategy and have community participate little
> > > bit more - Dev community is very active but QA is not at the same
> > > level. There are too many discussions in dev mailing list already.
> > > Afraid that QA may not get enough attention
> > >
> > > - Discuss project QA activities and track progress and
> > > present relevant info to community. Intention is not to take away
> > > visibility but to have a focused vision on QA.
> > >
> > > - Discuss other QA initiatives and have owners drive these
> > > initiatives - mainly around automation frameworks, tools
> > > implementation for QA
> > >
> > >
> > > Please do express your opinion on this.
> > >
> > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > activities starting next week as we are getting close to the
> > > release.
> > >
> >
> > Why not use the -users list? It's not high-traffic and QA are users
> > testing/using the product? It will encourage our users to test
> > alongside releases and participate in the testing process. Some of
> > our users I'm sure can contribute automated tests.
> >
> Including the users (+cross-posting)
>
>
> --
> Prasanna.,
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
RE: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Sudha Ponnaganti <su...@citrix.com>.
One of the concerns is that QA may not feel comfortable to discuss all the QA topics in Dev mailing list.
Would like to attract QA community to contribute more than just testing - development of tools and adoption of automation.
As is QA is not participating frequently and current dedicated effort is to accelerate that. I am not sure if that would be successful or not but I sense that QA is not feeling comfortable to discuss QA topics in Dev mailing lists. Several times QA folks are being nudged to post on dev mailing lists from few folks participated in 4.0 QA effort. That is why I thought this approach might help.
Intention is not to isolate this mailing list but to keep focus and encourage participation.
-----Original Message-----
From: Mohammad Nour El-Din [mailto:nour.mohammad@gmail.com]
Sent: Tuesday, December 18, 2012 3:17 PM
To: cloudstack-dev@incubator.apache.org; CloudStack Users
Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
Hi
Allow me to dis-agree with you about one minor point that differentiates frequest/planned/scheduled QA tasks or activities than than what users find while using ACS, I think what is proposed is related to the former point
The idea itself is appealing but the amount of interaction really needs separate mailing list ? Can we just send e-mail tagged with [QA] for example which then helps filter out QA related e-mails ?
On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam < prasanna.santhanam@citrix.com> wrote:
> On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > Hi All,
> > >
> > > Reaching out to community to see if we can have a dedicated QA
> > > mailing list mainly to have a focused attention around QA
> > > Activities.
> > >
> > >
> > > - To discuss automation acceleration. We already have
> > > sizable scripts and need to get those running in to apache env
> > >
> > > - Discuss QA strategy and have community participate little
> > > bit more - Dev community is very active but QA is not at the same
> > > level. There are too many discussions in dev mailing list already.
> > > Afraid that QA may not get enough attention
> > >
> > > - Discuss project QA activities and track progress and
> > > present relevant info to community. Intention is not to take away
> > > visibility but to have a focused vision on QA.
> > >
> > > - Discuss other QA initiatives and have owners drive these
> > > initiatives - mainly around automation frameworks, tools
> > > implementation for QA
> > >
> > >
> > > Please do express your opinion on this.
> > >
> > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > activities starting next week as we are getting close to the
> > > release.
> > >
> >
> > Why not use the -users list? It's not high-traffic and QA are users
> > testing/using the product? It will encourage our users to test
> > alongside releases and participate in the testing process. Some of
> > our users I'm sure can contribute automated tests.
> >
> Including the users (+cross-posting)
>
>
> --
> Prasanna.,
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi
Allow me to dis-agree with you about one minor point that differentiates
frequest/planned/scheduled QA tasks or activities than than what users find
while using ACS, I think what is proposed is related to the former point
The idea itself is appealing but the amount of interaction really needs
separate mailing list ? Can we just send e-mail tagged with [QA] for
example which then helps filter out QA related e-mails ?
On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
prasanna.santhanam@citrix.com> wrote:
> On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > Hi All,
> > >
> > > Reaching out to community to see if we can have a dedicated QA
> > > mailing list mainly to have a focused attention around QA
> > > Activities.
> > >
> > >
> > > - To discuss automation acceleration. We already have
> > > sizable scripts and need to get those running in to apache env
> > >
> > > - Discuss QA strategy and have community participate little
> > > bit more - Dev community is very active but QA is not at the same
> > > level. There are too many discussions in dev mailing list already.
> > > Afraid that QA may not get enough attention
> > >
> > > - Discuss project QA activities and track progress and
> > > present relevant info to community. Intention is not to take away
> > > visibility but to have a focused vision on QA.
> > >
> > > - Discuss other QA initiatives and have owners drive these
> > > initiatives - mainly around automation frameworks, tools
> > > implementation for QA
> > >
> > >
> > > Please do express your opinion on this.
> > >
> > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > activities starting next week as we are getting close to the
> > > release.
> > >
> >
> > Why not use the -users list? It's not high-traffic and QA are users
> > testing/using the product? It will encourage our users to test
> > alongside releases and participate in the testing process. Some of our
> > users I'm sure can contribute automated tests.
> >
> Including the users (+cross-posting)
>
>
> --
> Prasanna.,
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi
On Wed, Dec 19, 2012 at 12:16 AM, Alex Huang <Al...@citrix.com> wrote:
> The problem with using -users is that -qa will often have issues that are
> raised during nightly testing, etc. Exposing users is often too much
> detail.
>
Sorry that I didn't explain, I didn't mean using -uers at all and I believe
we should not using it, QA in the way I referred to is part of the
development process and hence this should go through the -dev list
>
> --Alex
>
> > -----Original Message-----
> > From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
> > Sent: Tuesday, December 18, 2012 3:12 PM
> > To: cloudstack-dev@incubator.apache.org; CloudStack Users
> > Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
> >
> > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > Hi All,
> > > >
> > > > Reaching out to community to see if we can have a dedicated QA
> > > > mailing list mainly to have a focused attention around QA
> > > > Activities.
> > > >
> > > >
> > > > - To discuss automation acceleration. We already have
> > > > sizable scripts and need to get those running in to apache env
> > > >
> > > > - Discuss QA strategy and have community participate little
> > > > bit more - Dev community is very active but QA is not at the same
> > > > level. There are too many discussions in dev mailing list already.
> > > > Afraid that QA may not get enough attention
> > > >
> > > > - Discuss project QA activities and track progress and
> > > > present relevant info to community. Intention is not to take away
> > > > visibility but to have a focused vision on QA.
> > > >
> > > > - Discuss other QA initiatives and have owners drive these
> > > > initiatives - mainly around automation frameworks, tools
> > > > implementation for QA
> > > >
> > > >
> > > > Please do express your opinion on this.
> > > >
> > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > activities starting next week as we are getting close to the
> > > > release.
> > > >
> > >
> > > Why not use the -users list? It's not high-traffic and QA are users
> > > testing/using the product? It will encourage our users to test
> > > alongside releases and participate in the testing process. Some of our
> > > users I'm sure can contribute automated tests.
> > >
> > Including the users (+cross-posting)
> >
> >
> > --
> > Prasanna.,
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi
On Wed, Dec 19, 2012 at 12:16 AM, Alex Huang <Al...@citrix.com> wrote:
> The problem with using -users is that -qa will often have issues that are
> raised during nightly testing, etc. Exposing users is often too much
> detail.
>
Sorry that I didn't explain, I didn't mean using -uers at all and I believe
we should not using it, QA in the way I referred to is part of the
development process and hence this should go through the -dev list
>
> --Alex
>
> > -----Original Message-----
> > From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
> > Sent: Tuesday, December 18, 2012 3:12 PM
> > To: cloudstack-dev@incubator.apache.org; CloudStack Users
> > Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
> >
> > On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > > Hi All,
> > > >
> > > > Reaching out to community to see if we can have a dedicated QA
> > > > mailing list mainly to have a focused attention around QA
> > > > Activities.
> > > >
> > > >
> > > > - To discuss automation acceleration. We already have
> > > > sizable scripts and need to get those running in to apache env
> > > >
> > > > - Discuss QA strategy and have community participate little
> > > > bit more - Dev community is very active but QA is not at the same
> > > > level. There are too many discussions in dev mailing list already.
> > > > Afraid that QA may not get enough attention
> > > >
> > > > - Discuss project QA activities and track progress and
> > > > present relevant info to community. Intention is not to take away
> > > > visibility but to have a focused vision on QA.
> > > >
> > > > - Discuss other QA initiatives and have owners drive these
> > > > initiatives - mainly around automation frameworks, tools
> > > > implementation for QA
> > > >
> > > >
> > > > Please do express your opinion on this.
> > > >
> > > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > > activities starting next week as we are getting close to the
> > > > release.
> > > >
> > >
> > > Why not use the -users list? It's not high-traffic and QA are users
> > > testing/using the product? It will encourage our users to test
> > > alongside releases and participate in the testing process. Some of our
> > > users I'm sure can contribute automated tests.
> > >
> > Including the users (+cross-posting)
> >
> >
> > --
> > Prasanna.,
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
RE: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Alex Huang <Al...@citrix.com>.
The problem with using -users is that -qa will often have issues that are raised during nightly testing, etc. Exposing users is often too much detail.
--Alex
> -----Original Message-----
> From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
> Sent: Tuesday, December 18, 2012 3:12 PM
> To: cloudstack-dev@incubator.apache.org; CloudStack Users
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > Hi All,
> > >
> > > Reaching out to community to see if we can have a dedicated QA
> > > mailing list mainly to have a focused attention around QA
> > > Activities.
> > >
> > >
> > > - To discuss automation acceleration. We already have
> > > sizable scripts and need to get those running in to apache env
> > >
> > > - Discuss QA strategy and have community participate little
> > > bit more - Dev community is very active but QA is not at the same
> > > level. There are too many discussions in dev mailing list already.
> > > Afraid that QA may not get enough attention
> > >
> > > - Discuss project QA activities and track progress and
> > > present relevant info to community. Intention is not to take away
> > > visibility but to have a focused vision on QA.
> > >
> > > - Discuss other QA initiatives and have owners drive these
> > > initiatives - mainly around automation frameworks, tools
> > > implementation for QA
> > >
> > >
> > > Please do express your opinion on this.
> > >
> > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > activities starting next week as we are getting close to the
> > > release.
> > >
> >
> > Why not use the -users list? It's not high-traffic and QA are users
> > testing/using the product? It will encourage our users to test
> > alongside releases and participate in the testing process. Some of our
> > users I'm sure can contribute automated tests.
> >
> Including the users (+cross-posting)
>
>
> --
> Prasanna.,
Re: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi
Allow me to dis-agree with you about one minor point that differentiates
frequest/planned/scheduled QA tasks or activities than than what users find
while using ACS, I think what is proposed is related to the former point
The idea itself is appealing but the amount of interaction really needs
separate mailing list ? Can we just send e-mail tagged with [QA] for
example which then helps filter out QA related e-mails ?
On Wed, Dec 19, 2012 at 12:11 AM, Prasanna Santhanam <
prasanna.santhanam@citrix.com> wrote:
> On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > Hi All,
> > >
> > > Reaching out to community to see if we can have a dedicated QA
> > > mailing list mainly to have a focused attention around QA
> > > Activities.
> > >
> > >
> > > - To discuss automation acceleration. We already have
> > > sizable scripts and need to get those running in to apache env
> > >
> > > - Discuss QA strategy and have community participate little
> > > bit more - Dev community is very active but QA is not at the same
> > > level. There are too many discussions in dev mailing list already.
> > > Afraid that QA may not get enough attention
> > >
> > > - Discuss project QA activities and track progress and
> > > present relevant info to community. Intention is not to take away
> > > visibility but to have a focused vision on QA.
> > >
> > > - Discuss other QA initiatives and have owners drive these
> > > initiatives - mainly around automation frameworks, tools
> > > implementation for QA
> > >
> > >
> > > Please do express your opinion on this.
> > >
> > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > activities starting next week as we are getting close to the
> > > release.
> > >
> >
> > Why not use the -users list? It's not high-traffic and QA are users
> > testing/using the product? It will encourage our users to test
> > alongside releases and participate in the testing process. Some of our
> > users I'm sure can contribute automated tests.
> >
> Including the users (+cross-posting)
>
>
> --
> Prasanna.,
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
RE: Request for cloudstack-qa mailing list and QA Scrum call
Posted by Alex Huang <Al...@citrix.com>.
The problem with using -users is that -qa will often have issues that are raised during nightly testing, etc. Exposing users is often too much detail.
--Alex
> -----Original Message-----
> From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
> Sent: Tuesday, December 18, 2012 3:12 PM
> To: cloudstack-dev@incubator.apache.org; CloudStack Users
> Subject: Re: Request for cloudstack-qa mailing list and QA Scrum call
>
> On Wed, Dec 19, 2012 at 04:38:57AM +0530, Prasanna Santhanam wrote:
> > On Wed, Dec 19, 2012 at 04:32:02AM +0530, Sudha Ponnaganti wrote:
> > > Hi All,
> > >
> > > Reaching out to community to see if we can have a dedicated QA
> > > mailing list mainly to have a focused attention around QA
> > > Activities.
> > >
> > >
> > > - To discuss automation acceleration. We already have
> > > sizable scripts and need to get those running in to apache env
> > >
> > > - Discuss QA strategy and have community participate little
> > > bit more - Dev community is very active but QA is not at the same
> > > level. There are too many discussions in dev mailing list already.
> > > Afraid that QA may not get enough attention
> > >
> > > - Discuss project QA activities and track progress and
> > > present relevant info to community. Intention is not to take away
> > > visibility but to have a focused vision on QA.
> > >
> > > - Discuss other QA initiatives and have owners drive these
> > > initiatives - mainly around automation frameworks, tools
> > > implementation for QA
> > >
> > >
> > > Please do express your opinion on this.
> > >
> > > Also I am going to setup a call to discuss ASF CS 4.1 release QA
> > > activities starting next week as we are getting close to the
> > > release.
> > >
> >
> > Why not use the -users list? It's not high-traffic and QA are users
> > testing/using the product? It will encourage our users to test
> > alongside releases and participate in the testing process. Some of our
> > users I'm sure can contribute automated tests.
> >
> Including the users (+cross-posting)
>
>
> --
> Prasanna.,