24PI2 Planning

[JillieBeanSim]

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

Important Dates

Planning 2024/04/23 - 2024/04/26

Kickoff - 04/16/2024 - 9:00 - 10:30 am ET
Opening (Day 1) - 04/24/2024 8:00 - 11:00 am ET
Thursday, April 25 - Breakouts (Optional) (Day 2)
Final Readouts (Day 3) - 04/26/2024 9:00 - 11:00 am ET

Releases

• 2.16.0 - May 13, 2024
• 2.17.0 - July 15, 2024
• 2.18.0 - Aug 26, 2024
• 3.0.0 - Sep 30, 2024

24Q2 Plan Objectives

Continue preparing for v3 GA with continued pre-release availability, wrapping up all breaking changes by end of PI.

• Support Certificate Authentication #2621 - (24Q1 rollover)
• Provide Client Side z/OSMF Certificate Support Zowe Explorer #2373 - (24Q1 rollover)
• next: Remove deprecated methods #2238 - Breaking change
• [vNext] DS Templates setting to be accessible and usable via workspace settings #2345 - Breaking change
• Double check scopes of settings for correctness #2303 - Breaking change
• Update ZE to use imperative's APIs for updating imperative.json  #2622
• Notify extenders when changes to the vault have been made #2546
• Add integration tests using WebdriverIO #2322
• Support logging in to multiple APIML instances per config file #2264 - stretch (24Q1 rollover)
• Design and Implement a user friendly UI for setting up and editing config profiles #2265 - stretch
• Tabular display option for Jobs tree #2258 - stretch
• Full text search across all the members, like ISPF SrchFor utility does #449 - stretch

Please users and extenders with continuous development of enhancements for upcoming v2.x releases.

• Cannot switch from basic auth. to token-based auth. #2590 - in progress (24Q1 rollover)
• Investigate support for mutli-root workspaces for documentation purposes #2386 - moving to v3.0.0 GA Release Plan
• Add link to log file #2271 - stretch
• Improve experience for using API ML sessions in Zowe Explorer #2252 - stretch

Reduce Zowe Explorer reported bug count by 20% by the end of the PI. (82 total bugs in repo as of 4/8/2024)

• ZOWE JOB Data does not refresh #2561 - (24Q1 rollover)
• ZE affecting multi select with VSC 1.87 #2798
• File keeps trying to be saved if not enough permissions #2627 - moving to v2.18.0 Release Plan
• Repeated attempt to save member despite S913 #2406 - moving to v2.18.0 Release Plan
• trying to create a new zosmf profile i now get "Error running command zowe.ds.addSession" #2800
• Issue with credentials not being up to date accross views #2465
• FTP profiles throw error after new credentials entered after 401 #2337 - moving to v2.18.0 Release Plan
• 'Remote file has been modified' loop when working with VB recfm #2327
• ZE's Delete keybindings broken with VSC 1.88 #2825
• Zowe Explorer: Log in/out to/from Authentication Service Keyboard Shortcuts not working #2294
• USS delete quick key broken #2796
• copy/paste keybinding not working correctly in USS tree view #2823
• Error when user clicks on favorited job #2618 - stretch
• Unexpected behavior in TSO Commands #2528 - moving to v2.18.0 Release Plan
• [zFTP] Data connection encryption field issue when updating a profile #1865 - stretch

CICS Related Issues (STRETCH)

• When a 401 response is received let the user know their credentials are invalid cics-for-zowe-client#61 - stretch
• Errors are not user-friendly cics-for-zowe-client#118 - stretch

Roadmap

Add more functionality to the Jobs tree view

COMPLETED

• What problem are you solving?
  • Users would like a comparable experience working with JES files, Zowe Explorer doesn't have a lot of functionality in that tree compared to others.
• What are you doing to solve it?
  • Add more functionality to jobs in the tree, ie. local sorting, filtering, and more.
• When do you plan to start the work?
  • 23Q1
• When do you plan to deliver the solution?
  • 24Q1

Zowe Explorer v3 GA

• What problem are you solving?
  • We have a great deal of items to complete for the v3 GA date and we don't want to miss anything important.
• *What are you doing to solve it?
  • Prepare a plan for dependency & engine updates, enhancements, migration tactics, and other items needed for our v3 GA release.
• When do you plan to start the work?
  • The work has been in progress since 23Q1
• When do you plan to deliver the solution?
  • ?

Improve experience for using API ML sessions in Zowe Explorer

• What problem are you solving?
  • Many users of Zowe Explorer aren't familiar with or are unaware of authentication methods supported by Zowe Explorer, like token authentication, SSO, & MFA.
• *What are you doing to solve it?
  • For users of the API ML with SSO and MFA, there are enhancements we could make to provide a more first-class experience.
• When do you plan to start the work?
  • 23Q3
• When do you plan to deliver the solution?
  • 24Q2

Tasks

Beta Give feedback

1. 24PI2 bug reduction of 20% #2836
   6 of 6
   Epic bug +2
2. Continuous development of enhancements for v2.x (24PI2) #2835
   2 of 2
   Epic enhancement +2
3. V3 work for 24PI2 #2220
   6 of 6
   Epic enhancement v3 +3
   

[JillieBeanSim]

Sprint dates

Sprint 1 - 2024/04/30 - 2024/05/13 (Innovation Sprint)
Sprint 2 - 2024/05/14 - 2024/05/27
Sprint 3 - 2024/05/28 - 2024/06/10
Sprint 4 - 2024/06/11 - 2024/06/24
Sprint 5 - 2024/06/25 - 2024/07/08
Sprint 6 - 2024/07/09 - 2024/07/22

[adam-wolfe]

Great list, we should also consider (possibly as stretches):

• Tabular display option for Jobs tree #2258
• Full text search across all the members, like ISPF SrchFor utility does #449

[JillieBeanSim]

Possible new Roadmap items for discussion, can be delivered late in the year early next year:

• Subsequent cleanup of interfaces and implementations of Zowe Explorer #497
  • has 2 open issues that may be solved by the new tree provider work.
• Enhance UI/UX for Zowe Explorer Webviews #2781
• Additional drag and drop functionality #2793

[JillieBeanSim]

@zFernand0 do we want any CICS items added to plan?

[JillieBeanSim]

Great list, we should also consider (possibly as stretches):

• Tabular display option for Jobs tree #2258
• Full text search across all the members, like ISPF SrchFor utility does #449

@adam-wolfe added as stretch to v3 objective, these items can easily be delivered after GA but thinking big wow enhancements should be v3 now with closing timeline to bring customers over once GA.

[adam-wolfe]

Great list, we should also consider (possibly as stretches):

• Tabular display option for Jobs tree #2258
• Full text search across all the members, like ISPF SrchFor utility does #449

@adam-wolfe added as stretch to v3 objective, these items can easily be delivered after GA but thinking big wow enhancements should be v3 now with closing timeline to bring customers over once GA.

Totally agree.

[adam-wolfe]

I think we will also want to include #2322

[JillieBeanSim]

added @adam-wolfe
also updated community ZE planning page

[zFernand0]

Hey @JillieBeanSim and @adam-wolfe,

CICS related issues

There are a few epics created in the CICS monorepo, but I do not believe we should commit to any of them for the time being.

If we want to commit to any CICS related work, I say we focus on reducing the number of open bugs in the monorepo. Here are some of the ones I consider most relevant:

• When a 401 response is received let the user know their credentials are invalid cics-for-zowe-client#61
• Errors are not user-friendly cics-for-zowe-client#118
• V1: Default protocol should be HTTPS, but get socket hang-up if missing cics-for-zowe-client#108 - v1: security
• V1: Unable to load properties from base profile cics-for-zowe-client#107 - v1: stretch

Finally, there are some high priority enhancements that we could have as stretch items here.

• Have option to create team config file cics-for-zowe-client#33 - stretch
• Allow the user to customise which resources they want to see via Settings cics-for-zowe-client#42 - stretch

Note: All issues listed above are in the priority that I believe will be most impactful to end users 😋

[adam-wolfe]

It may be worth also considering #2252 for the PI plan.

[adam-wolfe]

Spoke with Rose a bit about making a more descriptive roadmap. I tried to break the plan down into themes and problems. We can discuss this in planning. I think it might be challenging to try to depict something like this in a GitHub projects roadmap, but this is what I came up with:

[upon second thought, this table was not particularly useful]

[JillieBeanSim]

Hey @adam-wolfe thanks for putting the chart together, it seems to be the same information just broken down to show all the lowest level within a chart which is good for our wiki to give an in-depth view. With the GH Roadmap being tabular and able to step into each level easily within a GUI it may be ok to just update the Epics to reflect the Theme with description being the problem statement keeping the checklist of items to be worked on. What do you think?

[adam-wolfe]

Sounds good to me 👍

[JillieBeanSim]

closing plan, 24PI3 plan items v2.18.0 Release Plan & v3.0.0 GA Release Plan