Sig-release: Continue investigating triage-party for use within the release team

[markyjackson-taulia]

What would you like to be added:

Continue investigating triage-party for use within the release team

Why is this needed:

This tool will help with timely triaging as well and the bug-triage team during the release cycle.
@markyjackson-taulia did a presentation with @tstromberg during the release SIG meeting on 4/28/2020

[markyjackson-taulia]

/assign @markyjackson-taulia

[markyjackson-taulia]

/priority important-soon

[markyjackson-taulia]

@Verolop @xmudrii We can track our work with this issue and breakout where needed

[markyjackson-taulia]

Task breakout meeting set for 5/15. Working doc is here: https://docs.google.com/document/d/1p9XYRMT2dmIYBZxM9OwINjeRAGo5BwUeqZ8VTkklb0A/edit?usp=sharing

[markyjackson-taulia]

My apologies for not updating this issue in a timely manner.
@Verolop @xmudrii and I met on Monday to cover the tasks at hand. The doc here has been updated to reflect those items: https://docs.google.com/document/d/1p9XYRMT2dmIYBZxM9OwINjeRAGo5BwUeqZ8VTkklb0A/edit?usp=sharing

[justaugustus]

Keep up the great work!

[ameukam]

@Verolop @xmudrii FYI: https://github.com/kubernetes/k8s.io/issues/906

[markyjackson-taulia]

This can be closed as @ameukam is working through the final bit with dns but this investigation is completed.
/close

[justaugustus]

Let's continue to track this until Triage Party is live for SIG Release.
/reopen

[k8s-ci-robot]

@justaugustus: Reopened this issue.

In response to this:

Let's continue to track this until Triage Party is live for SIG Release.
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[markyjackson-taulia]

My bad, should have talked to more people before just closing. Won't happen again.

[justaugustus]

Not a big deal. Just want to make sure we close the loop. :)
/assign @ameukam @Verolop @xmudrii

[LappleApple]

/assign

[tstromberg]

Anything I can do to help support Triage Party in Kubernetes?

We just released Triage Party v1.3.0, which is mostly a stability release: https://github.com/google/triage-party/releases/tag/1.3.0

[LappleApple]

Heya, my effort to drive a layout prototype for the RT's version got pushed back due to a few personal and K8s-related developments, but I'll be on this topic again over the next three days.

[LappleApple]

Update: I've shared the prototype doc in my regular Monday session with the Release leads and then yesterday with a broader group at the 1.19 Release Team retro. Seems like we could move forward with setting up the details of the board.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[ameukam]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[puerco]

/remove-lifecycle stale

[LappleApple]

@ameukam @Verolop Hey, anything more to do here? :)

[ameukam]

We now have an instance (https://release.triage.k8s.io) running on aaa cluster : https://github.com/kubernetes/k8s.io/tree/main/triage-party/release-team. Over time, we are facing some issues but tstromberg is working to address them (Thank you! ❤️).

IIRC, @Verolop is working on a configuration for TP. Maybe we should adjust it to v1.22.
IMHO, next step would be collect wishes from SIG-Release about what need to be add. (can be a separate issue)

[LappleApple]

Hey folks, given the progress made last week with configuration can we close this item now? cc @cpanato @kubernetes/sig-release-leads

[cpanato]

@LappleApple I think we can close this for now and open new ones if needed after we play a bit with it

Did a small or to adjust some config and after that, we can close this

[ameukam]

+1 for closing once https://github.com/kubernetes/k8s.io/pull/1852 is merged and deployed.

[ameukam]

Oups. Bot took over when I mentioned the PR. Sorry.