You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Joseph Lynch <jo...@gmail.com> on 2018/11/07 20:04:16 UTC
4.0 Testing Signup
Following up on Jon's call
<https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E>
for QA, I put together the start of a confluence page
<https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup>for
people to list out important components that they think should be tested
before 4.0 releases and hopefully committers and contributors can signup
and present their progress to the community. I've certainly missed a ton of
components that need testing but I figured that it may be good to get the
conversation started and moving forward.
What do people think? Is there a more effective way to list these out or if
people like this maybe folks can start contributing sections and
volunteering to shepherd or test them?
Let me know,
-Joey
Re: 4.0 Testing Signup
Posted by Scott Andreas <sc...@paradoxica.net>.
Tommy, thank you! I’ve added your name as a contributor toward upgrade testing.
Thanks also for all of the work you’ve done toward this already, filing CASSANDRA-{14820, 14836, 14841, 14842, 14848}. The testing you’ve done so far, patches contributed, and issues reported are all great finds.
To edit pages in the wiki space, you’ll need to create an account here: https://cwiki.apache.org/confluence/signup.action. After doing that, email me (or this list) and I’ll add edit permissions for the wiki space.
[ Also, an apology to Joey and Nate – I tweaked the title of the doc, but didn’t realize that would alter the permalink. ]
On November 8, 2018 at 11:34:06 PM, Tommy Stendahl (tommy.stendahl@ericsson.com<ma...@ericsson.com>) wrote:
Hi,
I like to add myself as contributor under Cluster Upgrade but I could
not edit the page, could you please help.
I have already done some testing in this are lately and created a few
jiras, two remains open CASSANDRA-14842 and CASSANDRA-14848.
Thanks, Tommy
On 2018-11-08 23:30, Joseph Lynch wrote:
> On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin <ro...@yahoo.fr.invalid>
> wrote:
>
>> Hi,
>> I'm volunteer to be contributor on Metrics or Tooling component. Are we
>> supposed/allowed to edit Confluence page directly?Btw I think that tooling
>> should be split, maybe one ticket per tool?
>>
> Awesome! Yes feel free to add yourself as a contributor to whichever
> component you can contribute testing to (I think you need to make an Apache
> confluence account to do so), if it isn't working let me know and I'll add
> your contact information. Right now we don't have a shepherd for either
> component yet but I think it's pretty reasonable to have a tracking ticket
> that either has subtasks for each tool (e.g. CASSANDRA-14746) or just use
> linking (e.g. CASSANDRA-14697). Just try to describe in the tickets what
> kinds of tests you're running and make sure they're tagged with 4.0-QA
> label if possible.
>
> Thanks!
> - Joey
>
Re: 4.0 Testing Signup
Posted by Tommy Stendahl <to...@ericsson.com>.
Hi,
I like to add myself as contributor under Cluster Upgrade but I could
not edit the page, could you please help.
I have already done some testing in this are lately and created a few
jiras, two remains open CASSANDRA-14842 and CASSANDRA-14848.
Thanks, Tommy
On 2018-11-08 23:30, Joseph Lynch wrote:
> On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin <ro...@yahoo.fr.invalid>
> wrote:
>
>> Hi,
>> I'm volunteer to be contributor on Metrics or Tooling component. Are we
>> supposed/allowed to edit Confluence page directly?Btw I think that tooling
>> should be split, maybe one ticket per tool?
>>
> Awesome! Yes feel free to add yourself as a contributor to whichever
> component you can contribute testing to (I think you need to make an Apache
> confluence account to do so), if it isn't working let me know and I'll add
> your contact information. Right now we don't have a shepherd for either
> component yet but I think it's pretty reasonable to have a tracking ticket
> that either has subtasks for each tool (e.g. CASSANDRA-14746) or just use
> linking (e.g. CASSANDRA-14697). Just try to describe in the tickets what
> kinds of tests you're running and make sure they're tagged with 4.0-QA
> label if possible.
>
> Thanks!
> - Joey
>
Re: 4.0 Testing Signup
Posted by Joseph Lynch <jo...@gmail.com>.
On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin <ro...@yahoo.fr.invalid>
wrote:
>
> Hi,
> I'm volunteer to be contributor on Metrics or Tooling component. Are we
> supposed/allowed to edit Confluence page directly?Btw I think that tooling
> should be split, maybe one ticket per tool?
>
Awesome! Yes feel free to add yourself as a contributor to whichever
component you can contribute testing to (I think you need to make an Apache
confluence account to do so), if it isn't working let me know and I'll add
your contact information. Right now we don't have a shepherd for either
component yet but I think it's pretty reasonable to have a tracking ticket
that either has subtasks for each tool (e.g. CASSANDRA-14746) or just use
linking (e.g. CASSANDRA-14697). Just try to describe in the tickets what
kinds of tests you're running and make sure they're tagged with 4.0-QA
label if possible.
Thanks!
- Joey
Re: 4.0 Testing Signup
Posted by Nate McCall <zz...@gmail.com>.
Thanks Romain!
Let's keep a top level ticket for the/a component, but add child tasks
as needed. I think child tickets are a little easier to manage than
using a tag or similar.
On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin
<ro...@yahoo.fr.invalid> wrote:
>
>
> Hi,
> I'm volunteer to be contributor on Metrics or Tooling component. Are we supposed/allowed to edit Confluence page directly?Btw I think that tooling should be split, maybe one ticket per tool?
> Thanks,
> Romain Le mercredi 7 novembre 2018 à 22:51:30 UTC+1, sankalp kohli <ko...@gmail.com> a écrit :
>
> This is good start and we should use this approach each component. Once we
> have volunteers for each area, it will be important to also publish a
> confluence page per component by the volunteer so we can know/discuss how
> it was tested.
>
> On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch <jo...@gmail.com> wrote:
>
> > Following up on Jon's call
> > <
> > https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E
> > >
> > for QA, I put together the start of a confluence page
> > <https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup>for
> > people to list out important components that they think should be tested
> > before 4.0 releases and hopefully committers and contributors can signup
> > and present their progress to the community. I've certainly missed a ton of
> > components that need testing but I figured that it may be good to get the
> > conversation started and moving forward.
> >
> > What do people think? Is there a more effective way to list these out or if
> > people like this maybe folks can start contributing sections and
> > volunteering to shepherd or test them?
> >
> > Let me know,
> > -Joey
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: 4.0 Testing Signup
Posted by Romain Hardouin <ro...@yahoo.fr.INVALID>.
Hi,
I'm volunteer to be contributor on Metrics or Tooling component. Are we supposed/allowed to edit Confluence page directly?Btw I think that tooling should be split, maybe one ticket per tool?
Thanks,
Romain Le mercredi 7 novembre 2018 à 22:51:30 UTC+1, sankalp kohli <ko...@gmail.com> a écrit :
This is good start and we should use this approach each component. Once we
have volunteers for each area, it will be important to also publish a
confluence page per component by the volunteer so we can know/discuss how
it was tested.
On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch <jo...@gmail.com> wrote:
> Following up on Jon's call
> <
> https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E
> >
> for QA, I put together the start of a confluence page
> <https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup>for
> people to list out important components that they think should be tested
> before 4.0 releases and hopefully committers and contributors can signup
> and present their progress to the community. I've certainly missed a ton of
> components that need testing but I figured that it may be good to get the
> conversation started and moving forward.
>
> What do people think? Is there a more effective way to list these out or if
> people like this maybe folks can start contributing sections and
> volunteering to shepherd or test them?
>
> Let me know,
> -Joey
>
Re: 4.0 Testing Signup
Posted by Scott Andreas <sc...@paradoxica.net>.
Joey, thanks for starting this document!
I’ve updated it to add several leads/contributors, and will probably have a few minor updates to add soon.
On November 8, 2018 at 2:49:52 PM, Joseph Lynch (joe.e.lynch@gmail.com<ma...@gmail.com>) wrote:
On Thu, Nov 8, 2018 at 1:42 PM kurt greaves <ku...@instaclustr.com> wrote:
> Been thinking about this for a while and agree it's how we should approach
> it. BIkeshedding but seems like a nice big table would be suitable here,
> and I think rather than a separate confluence page per component we just
> create separate JIRA tickets that detail what's being tested and the
> approach, and discussion can be kept in JIRA.
>
Can we let each component group figure out how they want to do project
management with the one caveat that they list the component on the page and
have a tracking ticket with the right label? I think that's the lightest
touch process that will work.
> I'm happy to volunteer for testing repair. I can also add lots of different
> components to the list if you're happy for me to attack the page.
>
Go for it! I just jotted down some seed topics to get it started. Please do
edit and refactor to make it better.
-Joey
Re: 4.0 Testing Signup
Posted by Joseph Lynch <jo...@gmail.com>.
On Thu, Nov 8, 2018 at 1:42 PM kurt greaves <ku...@instaclustr.com> wrote:
> Been thinking about this for a while and agree it's how we should approach
> it. BIkeshedding but seems like a nice big table would be suitable here,
> and I think rather than a separate confluence page per component we just
> create separate JIRA tickets that detail what's being tested and the
> approach, and discussion can be kept in JIRA.
>
Can we let each component group figure out how they want to do project
management with the one caveat that they list the component on the page and
have a tracking ticket with the right label? I think that's the lightest
touch process that will work.
> I'm happy to volunteer for testing repair. I can also add lots of different
> components to the list if you're happy for me to attack the page.
>
Go for it! I just jotted down some seed topics to get it started. Please do
edit and refactor to make it better.
-Joey
Re: 4.0 Testing Signup
Posted by kurt greaves <ku...@instaclustr.com>.
Been thinking about this for a while and agree it's how we should approach
it. BIkeshedding but seems like a nice big table would be suitable here,
and I think rather than a separate confluence page per component we just
create separate JIRA tickets that detail what's being tested and the
approach, and discussion can be kept in JIRA.
I'm happy to volunteer for testing repair. I can also add lots of different
components to the list if you're happy for me to attack the page.
On Thu, 8 Nov 2018 at 08:51, sankalp kohli <ko...@gmail.com> wrote:
> This is good start and we should use this approach each component. Once we
> have volunteers for each area, it will be important to also publish a
> confluence page per component by the volunteer so we can know/discuss how
> it was tested.
>
> On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch <jo...@gmail.com>
> wrote:
>
> > Following up on Jon's call
> > <
> >
> https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E
> > >
> > for QA, I put together the start of a confluence page
> > <https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup>for
> > people to list out important components that they think should be tested
> > before 4.0 releases and hopefully committers and contributors can signup
> > and present their progress to the community. I've certainly missed a ton
> of
> > components that need testing but I figured that it may be good to get the
> > conversation started and moving forward.
> >
> > What do people think? Is there a more effective way to list these out or
> if
> > people like this maybe folks can start contributing sections and
> > volunteering to shepherd or test them?
> >
> > Let me know,
> > -Joey
> >
>
Re: 4.0 Testing Signup
Posted by sankalp kohli <ko...@gmail.com>.
This is good start and we should use this approach each component. Once we
have volunteers for each area, it will be important to also publish a
confluence page per component by the volunteer so we can know/discuss how
it was tested.
On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch <jo...@gmail.com> wrote:
> Following up on Jon's call
> <
> https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E
> >
> for QA, I put together the start of a confluence page
> <https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup>for
> people to list out important components that they think should be tested
> before 4.0 releases and hopefully committers and contributors can signup
> and present their progress to the community. I've certainly missed a ton of
> components that need testing but I figured that it may be good to get the
> conversation started and moving forward.
>
> What do people think? Is there a more effective way to list these out or if
> people like this maybe folks can start contributing sections and
> volunteering to shepherd or test them?
>
> Let me know,
> -Joey
>