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 230 #21925

Closed
39 of 60 tasks
ibuziuk opened this issue Jan 9, 2023 · 3 comments
Closed
39 of 60 tasks

Sprint 230 #21925

ibuziuk opened this issue Jan 9, 2023 · 3 comments
Labels
kind/planning A checklist of issues for planning a particular sprint. sprint/current

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jan 9, 2023

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

The previous sprint #21864

Sprint goals

  • Daily periodic tests for Developer Sandbox stg, m1, m2, m3 clusters

Aditional Notes

Sprint tasks

WTO

DWO

Dashboard

Che Operator

chectl

Che Server

Technical Debt

Developer Sandbox

  • Daily periodic tests for Developer Sandbox stg, m1, m2, m3 clusters @ScrewTSW

Image Puller

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] ... 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:

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 Jan 9, 2023
@ibuziuk ibuziuk added kind/planning A checklist of issues for planning a particular sprint. sprint/next status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 9, 2023
@amisevsk amisevsk changed the title Sprint 330 Sprint 230 Jan 9, 2023
@nickboldt
Copy link
Contributor

nickboldt commented Jan 10, 2023

Productization

Security:

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 issues to consider:

Future issues (3.5 or 3.6 - depends on approval from Kasturi or Rick):

  • CRW-3489 Drop theia from list of available editors in dashboard
  • CRW-3662 Enable theia IDE removal warning in dashboard
  • CRW-3514 Remove CRW 2.15 jobs from Jenkins

@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 Jan 10, 2023
@nickboldt
Copy link
Contributor

nickboldt commented Jan 19, 2023

@ibuziuk ibuziuk closed this as completed Jan 25, 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

3 participants