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 231 (Team A) #21941

Closed
ibuziuk opened this issue Jan 19, 2023 · 8 comments
Closed

Sprint 231 (Team A) #21941

ibuziuk opened this issue Jan 19, 2023 · 8 comments
Labels
kind/planning A checklist of issues for planning a particular sprint. sprint/current status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Milestone

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jan 19, 2023

This issue collects work items of the Eclipse Che Team for Sprint 231 (January 25th - February 14th) (three weeks).
📓 Please note that this is a tentative plan until sprint planning has been conducted (January 25th)

Sprint goals

  • Release Che 7.60 (January 25th)
  • Release Dev Spaces 3.4, and promote it to Developer Sandbox workspaces.openshift.com (February 6th - February 9th)
  • Daily periodic tests for Developer Sandbox stg, m1, m2, m3 clusters
  • Improve git services OAuth flow
  • Pre-release testing of Dev Spaces 3.4.0.GA
  • Dev Spaces factory E2E acceptance tests automation
  • Happy path E2E GUI acceptance tests automation

Aditional Notes

  • Compliance and Ethics Training until January 31
  • Hack 'n' Hustle - February 3rd

Sprint Backlog

https://github.com/eclipse/che/labels/area%2Fgit%2Foauth-services

https://github.com/eclipse/che/labels/area%2Fdashboard

https://github.com/eclipse/che/labels/area%2Fche-operator

https://github.com/eclipse/che/labels/area%2Fchectl

https://github.com/eclipse/che/labels/kind%2Ftechnical-debt

https://github.com/eclipse/che/labels/area%2Fche-server

https://github.com/eclipse/che/labels/area%2Fplugin-registry

https://github.com/eclipse/che/labels/area%2Fdevfile-registry

https://github.com/eclipse/che/labels/area%2Fsamples

  • Using breakpoint for Node.js stacks with Vs Code editor is unclear CRW-3435

https://github.com/eclipse/che/labels/area%2Fimage-puller

  • N / A

https://github.com/eclipse/che/labels/area%2Fwebsite

https://github.com/eclipse/che/labels/area%2Fhosted-che

Browser Extension

Try in Web IDE GitHub action

https://github.com/eclipse/che/labels/area%2Fqe + https://github.com/eclipse/che/labels/e2e-test%2Ffailure + image

https://github.com/eclipse/che/labels/kind%2Frelease + https://github.com/eclipse/che/labels/area%2Fci + image

  • Release Che 7.60
  • Release Dev Spaces 3.4.0.GA
  • CRW-3765 update machine-exec dependencies for GHSA-6vm3-jj99-7229
  • CRW-3882 enable jiralint for CRW JIRA
  • CRW-3868 support building OSBS scratch builds from midstream PRs
  • CRW-3160 migrate code-rhel8 build to use cachito w/ yarn
  • CRW-3877 Allow to deploy DevSpaces from the latest IIB, fast channel using dsc -- possible H&H to learn a bit about typescript?

Prod Backlog A:

  • CRW-3601 in PR comments, switch from comments API to review-comments so we can update 'job started' to 'job done' messages
  • Triage / resolve CVE issues

https://github.com/eclipse/che/labels/area%2Fdoc

@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 19, 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 19, 2023
@nickboldt nickboldt mentioned this issue Jan 19, 2023
60 tasks
@ibuziuk ibuziuk added the team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che label Jan 23, 2023
@nickboldt nickboldt added this to the 7.61 milestone Jan 23, 2023
@nickboldt
Copy link
Contributor

Future prod 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

@nickboldt
Copy link
Contributor

Possible issues for this/next sprint:

  • CRW-3865 include sdkman in downstream UDI container?
  • CRW-3072 Include jbang binary in Universal Developer image

@l0rd
Copy link
Contributor

l0rd commented Jan 25, 2023

I have opened this issue on the git services support related to one of customers top requests (spreadsheet).

@ibuziuk ibuziuk added the area/git/oauth-services OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts label Jan 25, 2023
@ibuziuk
Copy link
Member Author

ibuziuk commented Jan 25, 2023

thanks, @l0rd I added the dedicated label for oauth services in the planning + one of the goals for the current sprint is the improvement of the git services OAuth flow since we already have quite a few bugs for this area

@ibuziuk ibuziuk removed the area/git/oauth-services OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts label Jan 25, 2023
@ibuziuk ibuziuk mentioned this issue Feb 8, 2023
56 tasks
@pmkovar
Copy link

pmkovar commented Feb 13, 2023

@ibuziuk
Copy link
Member Author

ibuziuk commented Feb 15, 2023

@pmkovar could you please, provide the scrum board for the next sprint to #21991?

@ibuziuk ibuziuk closed this as completed Feb 15, 2023
@pmkovar
Copy link

pmkovar commented Feb 27, 2023

@ibuziuk Added though note the link doesn't change in between the sprints, it's a permalink essentially.

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 status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Development

No branches or pull requests

5 participants