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

24PI2 Planning #2070

Closed
13 of 23 tasks
adam-wolfe opened this issue Feb 26, 2024 · 0 comments
Closed
13 of 23 tasks

24PI2 Planning #2070

adam-wolfe opened this issue Feb 26, 2024 · 0 comments
Labels
keep Issues with this label will be ignored by the stale bot

Comments

@adam-wolfe
Copy link
Contributor

adam-wolfe commented Feb 26, 2024

Zowe CLI Squad - 24PI2 - (2024/04/23 - 2024/07/22)

V3 Preparation

Implement planned changes for V3 and continue to publish pre-release versions to npm.

Repo maintenance

These items require updates to documentation in GitHub.

Other:

Config Usability

Continue to improve team config robustness and flexibility.

Extension Support

Ensure that extenders have access to the tools they need to interact with team config and secure credential storage.

High Priority and Upvoted Defects and Enhancements

Continue to responsibly address backlog items according to perceived priority and community interest.

SDK Conformance and LTS status

Finalize Zowe Client SDK conformance criteria and ensure that the Zowe Client Node.js SDK fulfills the criteria.

Stretch Issues - Added 4/19/2024

Zowe CLI / Zowe SDK Roadmap

Support connections to multiple APIML gateways through profile linking

  • _What problem are you solving?
    • Users cannot use team config to access services behind multiple APIML gateways.
  • _What are you doing to solve it?
    • Allow users to optionally specify explicit profile links in team configs - initially to link a service profile to a base (APIML) profile, so that Zowe CLI and Zowe Explorer can identify which APIML connection to use for a given service profile.
  • _When do you plan to start the work?
    • CY24Q2
  • _When do you plan to deliver the solution?
    • CY24Q2

Searching

  • _What problem are you solving?
    • Users are not able to easily locate a data set, member, or spool file that contains information that they are looking for.
  • _What are you doing to solve it?
    • Give users the ability to search data sets, PDS members, or spool files for a given string, returning a list of files that contain the string and line numbers for each occurrence of the string in the file.
  • _When do you plan to start the work?
    • CY24Q1
  • _When do you plan to deliver the solution?
    • CY24Q2

Zowe client software event notification system

  • _What problem are you solving?
    • The Zowe client software (Zowe CLI, Zowe Client SDKs, Zowe Explorer for VS Code, and Zowe Explorer for IntelliJ) have no way of knowing what actions the user has taken in other Zowe Client software (e.g., if the user changes a password in Zowe CLI, Zowe Explorer for VS Code will not know to reload the credentials from disk).
  • _What are you doing to solve it?
    • Implement a system for sharing event notifications (such as a user updating a password) that can be shared by all Zowe Client software regardless of programming language or runtime environment.
  • _When do you plan to start the work?
    • CY24Q1
  • _When do you plan to deliver the solution?
    • CY24Q2

SDK Conformance and LTS Status

  • _What problem are you solving?
    • Mainframe developers are interested in extending the existing SDKs in order to create applications for their services
  • _What are you doing to solve it?
    • Solidify the SDK Conformance guidelines for:
      • New Services (like CICS SDK)
      • New Programming languages (like Kotlin SDK)
    • Prepare the SDKs technically and logistically for conformance
    • Determine if existing SDKs are conformant and communicate conformance gaps for prioritization
    • Release the Zowe Client Node.js SDK as LTS
  • _When do you plan to start the work?
    • CY23Q2
  • _When do you plan to deliver the solution?
    • CY23Q4 (delayed until CY24Q2)

Gold OpenSSF Best Practices Badge (Formerly CII Best Practices Badge)

  • _What problem are you solving?
    • The Zowe Project has not earned the gold OpenSSF Best Practices Badge, a requirement from LF/OMP that ensures the Open-Source project satisfies FLOSS (Free/Libre & Open-Source Software) Best Practices criteria
  • _What are you doing to solve it?
    • Review requirements and take necessary actions to satisfy them for the gold badge level
  • _When do you plan to start the work?
    • CY22Q3
  • _When do you plan to deliver the solution?
    • CY24Q1 Achieve Passing Badge (delayed until CY24Q2)
    • CY24Q4 Achieve Silver Badge
    • CY25Q4 Achieve Gold Badge

(Completed) Ensure that Zowe VS Code Extensions can Share Access to zowe.schema.json with Zowe CLI

  • _What problem are you solving?
    • Zowe CLI overwrites team config profile entries contributed by Zowe Explorer extensions, preventing those extensions from being able to properly access profiles from a user's team config.
  • _What are you doing to solve it?
    • Schema profile additions will be synchronized in such a way that both VS Code extensions and Zowe CLI plug-ins can contribute to a schema without removing the profiles contributed by the other.
  • _When do you plan to start the work?
    • CY23Q4
  • _When do you plan to deliver the solution?
    • CY24Q1
@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad Feb 26, 2024
@adam-wolfe adam-wolfe pinned this issue Feb 27, 2024
@adam-wolfe adam-wolfe changed the title 24PI2 Planning - Placeholder 24PI2 Planning Apr 10, 2024
@adam-wolfe adam-wolfe added the keep Issues with this label will be ignored by the stale bot label Apr 25, 2024
@github-project-automation github-project-automation bot moved this from New Issues to Closed in Zowe CLI Squad Jul 22, 2024
@adam-wolfe adam-wolfe unpinned this issue Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep Issues with this label will be ignored by the stale bot
Projects
Status: Closed
Development

No branches or pull requests

1 participant