Skip to content
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

Provide a script that creates markdown report out of prescriptions for a package #21728

Open
fridex opened this issue Apr 6, 2022 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Apr 6, 2022

Is your feature request related to a problem? Please describe.

As discussed at the TF SIG build community meeting, let's provide a way to generate a markdown file for TensorFlow. This file should turn prescriptions into a README that can be put in a repository. It will keep knowledge about issues/improvements to TensorFlow application stack in a human-readable form.

@fridex fridex added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 6, 2022
@goern
Copy link
Member

goern commented Apr 7, 2022

sounds this is a user-facing feature, so lets push it to
/sig user-experience

/triage needs-information

@sesheta sesheta added sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/needs-information Indicates an issue needs more information in order to work on it. labels Apr 7, 2022
@sesheta
Copy link
Member

sesheta commented Jul 6, 2022

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.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 6, 2022
@mayaCostantini
Copy link
Contributor

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 6, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
@Gkrumbach07
Copy link
Member

Gkrumbach07 commented Nov 1, 2022

Possible Acceptence Criteria

  • create a script that creates markdown readme of all prescriptions for a specific package
    • Group first by type, then add table with informations, package versions, messages, and links
  • This script could be included into prescription refresh job and places the output file in the same folder as the prescription data.
  • Also have this script accessible from the prescription CLI to be run whenever needed

@mayaCostantini how does this look?

/triage accepted

@Gkrumbach07
Copy link
Member

/triage accepted

@sesheta sesheta added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Nov 1, 2022
@Gkrumbach07 Gkrumbach07 added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/needs-information Indicates an issue needs more information in order to work on it. labels Nov 1, 2022
@Gkrumbach07 Gkrumbach07 moved this from 🆕 New to 📋 Backlog in Planning Board Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

5 participants