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 <romainh...@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 > <kohlisank...@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 <joe.e.ly...@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-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
