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

Plugins Sprint 194/195 #18529

Closed
21 of 34 tasks
ericwill opened this issue Dec 3, 2020 · 3 comments
Closed
21 of 34 tasks

Plugins Sprint 194/195 #18529

ericwill opened this issue Dec 3, 2020 · 3 comments
Labels
kind/planning A checklist of issues for planning a particular sprint.

Comments

@ericwill
Copy link
Contributor

ericwill commented Dec 3, 2020

Sprint 194/195 (December 9th 2020 to January 19th 2021)

This sprint will result in the release of Che 7.24, and possibly Che 7.25.

Blockers

Epics

CRW

Bugs

Unplanned

Open PRs From Last Sprint

Maintenance / Automation / Technical Debt / Tests

Theia API

Automation / Tests

Maintenance

Analysis

Availability

Name Availability 0.6x
@vitaliy-guliy 28 17
@vinokurig 22 13
@ericwill 15 9
@tsmaeder 19 11
@svor 27 16
@sunix 24 14

Priority Lists

@ericwill
Priority Item
1 Create a che-editors file to store all editors plugin definitions #18214
2 [CONTENT_UPDATE] AG - Customizing the devfile and plug-in registries documentation overly hard to read and understand RHDEVDOCS-1762
3 EUG] Create content for 'What is a devfile' section about 'A devfile as a a separate, locally stored artifact' RHDEVDOCS-2300
4 Use oc binary from oc tools rpm instead of kubectl binary from google CRW-1401
5 Use 3rd party icons in CRW plugin registry instead of invisble ones CRW-1385
@tsmaeder
Priority Item
1 VS Code extensions providing code snippets APIs make not usable in CRW CRW-1294
2 Update documentation of artifact repositories using untrusted TLS certificates RHDEVDOCS-2311
3 Rework che-theia build process to not use source linking #16852
@svor
Priority Item
1 The "Deploy to OpenShift" command failed in the "RedHatFuse" workspace CRW-1409
2 URLs of the project sample are not established after running the "2. Start Quarkus in devmode"in the "Quarkus" workspace CRW-1411
3 Failed to deploy sample to the Openshift cluster from the "NodeJS Configmap" based workspace CRW-1412
4 redhat/java plugin requires to declare a volume for dependencies stored in m2 CRW-1418
5 remove unneeded node / update to node 12 in sidecars CRW-1421
6 Support EAP XP 2.0 CRW-1419
7 Ability to run tests of a vscode extension on top of che-theia #18219
8 Update netcoredbg plugin #18462
@vinokurig
Priority Item
1 Apply CommentController plugin API eclipse-theia/theia#8492
2 Consider adding VS Code GitHub Pull Request plug-in to CRW 2.6 CRW-1226
3 Check if the GitHub oAuth is available when asking to sign in the Pull Requests plugin #18237
@vitaliy-guliy
Priority Item
1 Failure to clone zip projects when using OpenShift trusted CA bundle #18654
2 Add resource limits/requests to the devfiles and plugins in the registries #16685
3 Check for credentials (SSH) before trying to clone git repositories: #13494 (comment)
@sunix
Priority Item
1 Asciidoc export to pdf fails #16370
2 The rust getting started sample should use the vscode extension #17069
3 Importing several private projects in a single devfile fails #18494
4 [UX] When clicking "Run" nothing happens unless a java file is open / extension is loaded #18004
5 Check extensions of VS Code extension pack are running smoothly #15390
6 Update sonarlint-vscode to 1.17.0 #609
@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 3, 2020
@yhontyk yhontyk added kind/planning A checklist of issues for planning a particular sprint. team/plugins and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 4, 2020
@ericwill ericwill mentioned this issue Dec 9, 2020
34 tasks
@benoitf
Copy link
Contributor

benoitf commented Dec 9, 2020

As reported during prio call, please remove the line 'Rework che-theia build process to not use source linking #16852'
Also it's in a bug section while it's not even a bug
This enhancement is not even requested by PM/Architects or highly voted by people

@ericwill
Copy link
Contributor Author

ericwill commented Dec 9, 2020

As reported during prio call, please remove the line 'Rework che-theia build process to not use source linking #16852'
Also it's in a bug section while it's not even a bug

You're right, it's not a bug, and I have moved it to the maintenance section.

This enhancement is not even requested by PM/Architects or highly voted by people

It has been prioritized at the bottom of the queue for this sprint. Just because PM/Architects didn't request does not mean it cannot be worked on. As I understand it, @tsmaeder would like this enhancement to make his development flow easier. As long as PM/Architect priorities are being worked on, I don't see why we cannot work on this as well.

@ericwill
Copy link
Contributor Author

Superseded by #18808

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.
Projects
None yet
Development

No branches or pull requests

4 participants