Scott, thanks for the summary. Apparently I still haven't been successful
in communicating the kind of discussion around tradeoffs I want to have, or
maybe it comes off like I'm asking you to do my homework for me.
I'll put some more time into this, and I'll start a new thread hopefully
tomorrow.
Hey Stefan,
Thank you for your response.
“If it was feasible to gather all related changes touching a subsystem
under one umbrella ticket, that would be very nice but I do not know
if that makes sense from your point of view (what workflow you have).”
It is up to us to decide what would be the m
I personally rarely push tickets/post a patch in an raw state, but since I
almost always have to approve jobs when it gets close to commit, I don't
mind also confirming utest runs. I'd say it'd be good to run at very least
a compilation step on every commit. I think it's fine if dtests/utests/jvm
t
