Xinru Zhang

/remove-lifecycle stale

/release-note-none

/assign @jerop

/release-note-none

/kind documentation

/unhold Thanks @lbernick for pointing it out! Updated the doc. To reflect what we discussed, basically, the behavior of Run should be aligned with PipelineTask -- timeout is for each...

Thanks @lbernick, that's a great concern. Thanks @dibyom for your input. What I can think of we need to do is: creating an issue to - Clarify the retry behavior...

Though I do think it would be better if we keep the behaviors of Runs & TaskRuns aligned, then the action item would be what's the process of making breaking...

Opened a TEP (TEP-0121 https://github.com/tektoncd/community/pull/816) to fully discuss the behavior of retries, we can continue our discussions there.

As discussed in the [Tekton API Working Group](https://docs.google.com/document/d/17PodAxG8hV351fBhSu7Y_OIPhGTVgj6OJ2lPphYYRpU/edit#bookmark=id.jmjb8ox1pxln) today, we'd like to modify the development guidance of Custom Task, suggesting users to set timeout for each retry attempt.