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 233 (Team B) #22035

Closed
4 of 7 tasks
l0rd opened this issue Mar 6, 2023 · 7 comments
Closed
4 of 7 tasks

Sprint 233 (Team B) #22035

l0rd opened this issue Mar 6, 2023 · 7 comments
Labels
kind/planning A checklist of issues for planning a particular sprint. sprint/current team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.

Comments

@l0rd
Copy link
Contributor

l0rd commented Mar 6, 2023

This issue collects work items of the Eclipse Che https://github.com/eclipse/che/labels/team%2FB for Sprint 233 (Mar 9th - Mar 22th) (two weeks).

Continued from previous sprint #22001

📓 Please note that this is a tentative plan until sprint planning has been conducted (February 8th)

Red Hat DevTools Week Activities

@amisevsk:

@azatsarynnyy:

@AObuchow:

  • Learning about DWO/WTO release and productization process

@RomanNikitenko:

@vitaliy-guliy:

  • Explore possible ways to speed up Che-Code development:
    • Build the che-code by hands
    • How to run unit tests
    • Build the che-code docker image without running tests

@SDawley

@mkuznyetsov:

  • Eclipse Che Operator
  • Devworkspace Operator

@musienko-maxim:
Pick up/study tasks according to decisions in the issue: https://issues.redhat.com/browse/CRW-4093

@SkorikSergey
Security Journey course

@nallikaea: Devfiles

@l0rd:

  • recording 3 minute videos of devspaces-demo
  • devworkspace operator blog post

Sprint backlog

## AREA/DEVFILE-SPEC

## AREA/DEVWORKSPACE-OPERATOR

## AREA/WEB-TERMINAL

## AREA/EDITOR/VSCODE

## AREA/EDITOR/JETBRAIN

## AREA/UDI

## AREA/QE

## E2E-TEST/FAILURE

## AREA/CI

## KIND/RELEASE

## KIND/TASK

@l0rd l0rd added status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach sprint/next kind/planning A checklist of issues for planning a particular sprint. team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs. labels Mar 6, 2023
@azatsarynnyy

This comment was marked as outdated.

@nickboldt

This comment was marked as resolved.

@dmytro-ndp

This comment was marked as resolved.

@l0rd l0rd added sprint/current and removed status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach sprint/next labels Mar 8, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Mar 9, 2023

@amisevsk please consider that there is the new logs tab that is being working on by Team A

@l0rd
Copy link
Contributor Author

l0rd commented Mar 9, 2023

@AObuchow there is a DevTools activity that has been proposed in Team A backlog but is not assigned yet, that you could work on if interested:

Devfile Registry Operator https://github.com/devfile/registry-operator as a replaccement of https://github.com/eclipse-che/che-devfile-registry

@nickboldt
Copy link
Contributor

WIP for the current and next sprint: CRW-4049 Create jenkins build for vsix plugins, publishing to download.devel (subtask of [CRW-3336] pluginregistry :: Use fetch-artifacts for plugin registry build assets)

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 team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.
Projects
None yet
Development

No branches or pull requests

4 participants