Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

RFC-592 staging env Tracking issue #31695

Closed
44 of 47 tasks
jhchabran opened this issue Feb 23, 2022 · 2 comments
Closed
44 of 47 tasks

RFC-592 staging env Tracking issue #31695

jhchabran opened this issue Feb 23, 2022 · 2 comments
Assignees
Labels

Comments

@jhchabran
Copy link
Contributor

jhchabran commented Feb 23, 2022

Resources

Plan

Iteration 1

Iteration 2 ◀️

Iteration 3

  • Record a demo to communicate about all the changes

Tracked issues

@unassigned

Completed

@bobheadxi

Completed

@danieldides

Completed

@daxmc99

Completed

@filiphaftek

Completed

@jhchabran

Completed

@valerybugakov

Completed

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠️ Roadmap
  • 🕵️ Spike
  • 🔒 Security issue
  • 🙆 Stretch goal
@bobheadxi
Copy link
Member

bobheadxi commented Mar 22, 2022

Convenience link for DevX team work: https://github.com/sourcegraph/sourcegraph/issues?q=is%3Aopen+label%3Aokr%2FRFC-592+label%3Ateam%2Fdevx

Removed the DevX from the title because this issue seems to encompass devx and cloud work

@bobheadxi bobheadxi changed the title WIP: DevX RFC-592 Tracking issue WIP: RFC-592 Tracking issue Mar 22, 2022
@bobheadxi bobheadxi changed the title WIP: RFC-592 Tracking issue RFC-592 staging env Tracking issue Apr 6, 2022
@jhchabran
Copy link
Contributor Author

Closing this, as 90% of the work is done, and the remaining items are blocked for the time being or in flight.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants