-
Notifications
You must be signed in to change notification settings - Fork 1.3k
1-click export MVP Tracking issue #39588
Comments
Heads up @jplahn - the "team/repo-management" label was applied to this issue. |
(cc @kstretch9 because this might relate to the OpenTelemetry export stuff, either actually or just from a customer's POV) |
One-click export weekly updateWeek 2022/8/1 — 2022/8/5What is done
Goals for the next week
Risks
Notes
cc @jplahn |
@sashaostrikov - I just cleaned up our GitHub and these tracking issues may not be needed any longer! I tagged each ticket with the 1-click export Epic and created this view to show progress. Thoughts? |
@ryphil that's nice, thank you! I think I want to keep this issue just to have a single place of project updates, so it will also be easier for me to track the progress after I am back from PTO (instead of jumping across Slack channels searching for updates). But as soon as it is finished, we should close this ticket and continue working on post-MVP 1-click project in scope of your Epic :) |
@sourcegraph/delivery (which may be a legacy handle, but still) |
Plan
This is a tracking issue for 1-click export project MVP. Related discussion can be found here: https://github.com/sourcegraph/sourcegraph/discussions/37930
This issue can be considered closed when the MVP version of the project is implemented and 1-click export can be successfully used in production.
Due to its nature, 1-click export feature is easy to extend (by adding new processors which fetch additional data about SG instance), that's why this tracking issue is not intended to be open until 100% of 1-click export functionality is developed and on the contrary tracks the progress of an MVP version implementation. Every future extension (GH issue) can be linked to this issue and implemented separately, out of the scope of this tracking issue.
Tracked issues
@unassigned
Completed
#40190)@jhchabran
Completed
@sashaostrikov
Completed
#39813)#39855)#39813)#39880)#39962)#39962)#40078)Legend
The text was updated successfully, but these errors were encountered: