Re: [CI] What are the troubles projects face with CI and Infra
1 business driven tech debt creation 2 unwilling to do the up front investment 3 historic lack of trust in quality (unwilling to invest on test cases: no budget) = I find I learn more wisely by letting go of what I thought I knew: thus I listen deeper at the font of others' experiences. Daemeon Reiydelle USA 1.415.501.0198 On Sun, Feb 2, 2020, 13:52 Nate McCall wrote: > Hi folks, > The board is looking for feedback on CI infrastructure. I'm happy to take > some (constructive) comments back. (Shuler, Mick and David Capwell > specifically as folks who've most recently wrestled with this a fair bit). > > Thanks, > -Nate > > -- Forwarded message - > From: Dave Fisher > Date: Mon, Feb 3, 2020 at 8:58 AM > Subject: [CI] What are the troubles projects face with CI and Infra > To: Apache Board > > > Hi - > > It has come to the attention of the board through looking at past board > reports that some projects are having problems with CI infrastructure. > > Are there still troubles and what are they? > > Regards, > Dave >
Fwd: [CI] What are the troubles projects face with CI and Infra
Hi folks, The board is looking for feedback on CI infrastructure. I'm happy to take some (constructive) comments back. (Shuler, Mick and David Capwell specifically as folks who've most recently wrestled with this a fair bit). Thanks, -Nate -- Forwarded message - From: Dave Fisher Date: Mon, Feb 3, 2020 at 8:58 AM Subject: [CI] What are the troubles projects face with CI and Infra To: Apache Board Hi - It has come to the attention of the board through looking at past board reports that some projects are having problems with CI infrastructure. Are there still troubles and what are they? Regards, Dave
Re: Testing out JIRA as replacement for cwiki tracking of 4.0 quality testing
> > My .02: I think it'd improve our ability to collaborate and lower friction > to testing if we could do so on JIRA instead of the cwiki. *I suspect *the > edit access restrictions there plus general UX friction (difficult to have > collab discussion, comment chains, links to things, etc) make the confluent > wiki a worse tool for this job than JIRA. Plus if we do it in JIRA we can > track the outstanding scope in the single board and it's far easier to > visualize everything in one place so we can all know where attention and > resources need to be directed to best move the needle on things. > > But that's just my opinion. What does everyone else think? Like the JIRA > route? Hate it? No opinion? > > If we do decide we want to go the epic / JIRA route, I'd be happy to > migrate the rest of the information in there for things that haven't been > completed yet on the wiki (ticket creation, assignee/reviewer chains, links > to epic). > > So what does everyone think? > I think this is a good idea. Having the resources available to keep the various bits twiddled correctly on existing and new issues has always been the hard part for us. So regardless of the path, what we really need is some dedicated PM time going forward. Is that something you think you can help resource from your side? (Also, thanks for all the efforts exploring this either way!!)
