-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
open source testgrid dashboard, written in golang #3324
Comments
/assign @rmmh |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
AFAIK this is still ongoing |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale.
…On Sun, Jul 1, 2018, 16:36 fejta-bot ***@***.***> wrote:
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
<https://github.com/fejta>.
/lifecycle stale
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3324 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA4Bq4lOA_pNkvUWwrNCc4pNt-OOR2wzks5uCVztgaJpZM4OO990>
.
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
/lifecycle frozen |
This is still in progress; I'm actively working on it, and will update when the code is in a state to be open sourced (though it will need approval and validation after that before actually being publicly-viewable). |
Not much to say, but progress has been made on this and it is still chugging along. |
/milestone v1.13 |
Any more progress on this? Would love to have access to it for internal use. |
@michelle192837 is there any way for this to have a more granular progress bar that we could check ourselves without bugging you? |
Heya! Sorry about the lack of updates; this is slowly moving through bureaucracy internally, so I don't want to say much until I can say if it's approved for open sourcing officially. That said, while it's working its way through approvals I am still doing some other stuff to make sure it's ready for open sourcing to minimize approval -> release time. Once approved, I'll update here, and there should be more publicly-visible progress I can give. ^^ |
OK, sounds good! Just wanted to check if there was something easier than bugging you for updates :) |
Nah, feel free to bug me for updates. ^^ But I'll try and make it so you don't have to as often. |
/milestone 2019-goals It sure would be nice if we could do this in v1.14, but I'm going to defer to @michelle192837 to add back in to v1.14 milestone |
/milestone v1.16 |
Slating this for early next year. /milestone v1.18 ETA: Ah, darn. @spiffxp? |
@michelle192837: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. In response to this:
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. |
/milestone 2020-goals |
@spiffxp: The provided milestone is not valid for this repository. Milestones in this repository: [ Use In response to this:
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. |
/milestone 2020-goals also I think we should use a different team for /milestone in this repo, or get you added to milestone-maintainers |
/sig testing |
No description provided.
The text was updated successfully, but these errors were encountered: