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

Sprint 229 #21864

Closed
63 of 82 tasks
ibuziuk opened this issue Dec 5, 2022 · 3 comments
Closed
63 of 82 tasks

Sprint 229 #21864

ibuziuk opened this issue Dec 5, 2022 · 3 comments
Labels
kind/planning A checklist of issues for planning a particular sprint. sprint/current

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Dec 5, 2022

This issue collects work items of the Eclipse Che Team for Sprint 229 (December 14th - January 10th).
📓 Please note that this is a tentative plan until sprint planning has been conducted (December 13th)

The previous sprint #21823

Sprint goals

Aditional Notes

Sprint tasks

WTO

DWO

Dashboard

Operator

Che Server

chectl

Technical Debt

Developer Sandbox

Editors

Plugins

Productization

Tech Debt:

  • CRW-3080 Make Container Images Eligible for Source Containers (ongoing Epic)
    • CRW-3160 vscode :: migrate from pkgs.devel lookaside asset files to cachito w/ yarn [Nick]
    • CRW-3196 devfile registry :: migrate to fetch-artifacts (or commit files directly?) for sources [Sam]
    • CRW-3336 pluginregistry :: Use fetch-artifacts for plugin registry build assets

Che issues:

Other ideas:

  • CRW-3578 "NodeJS MongoDB" workspace recommendations have issues in VS Code Editor: vscode.typescript-language-features (not found in marketplace)
  • CRW-3581 enable github to jira integration (openshift-ci)
  • CRW-3601 in PR comments, switch from comments API to review-comments so we can update 'job started' to 'job done' messages

Docs

@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 5, 2022
@ibuziuk ibuziuk added kind/planning A checklist of issues for planning a particular sprint. sprint/next and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 5, 2022
@nickboldt
Copy link
Contributor

nickboldt commented Dec 7, 2022

Prod

Tech Debt:

  • CRW-3080 Make Container Images Eligible for Source Containers (ongoing Epic)
    • CRW-3160 vscode :: migrate from pkgs.devel lookaside asset files to cachito w/ yarn [Nick] ... in progress
    • CRW-3336 plugin registry :: Use fetch-artifacts for plugin registry build assets [Sam] ... in progress
    • CRW-3196 devfile registry :: migrate to fetch-artifacts (or commit files directly?) for sources

Che issues:

Other ideas:

  • CRW-3578 "NodeJS MongoDB" workspace recommendations have issues in VS Code Editor: vscode.typescript-language-features (not found in marketplace)
  • CRW-3581 enable github to jira integration (openshift-ci)
  • CRW-3601 in PR comments, switch from comments API to review-comments so we can update 'job started' to 'job done' messages

@ibuziuk ibuziuk added the status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach label Dec 9, 2022
@l0rd
Copy link
Contributor

l0rd commented Dec 13, 2022

@ibuziuk ibuziuk added sprint/current and removed sprint/next status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels Dec 13, 2022
@nickboldt
Copy link
Contributor

For next sprint, we should look at untriaged/unplanned/unowned issues in https://issues.redhat.com/browse/CRW-3623?jql=project%20%3D%20CRW%20AND%20type%20not%[…]s%20EMPTY%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC and decide if any should be done for 3.4/3.5.

@ibuziuk ibuziuk mentioned this issue Jan 9, 2023
60 tasks
@ibuziuk ibuziuk closed this as completed Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/planning A checklist of issues for planning a particular sprint. sprint/current
Projects
None yet
Development

No branches or pull requests

4 participants