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 #2799

Open
3 tasks
JillieBeanSim opened this issue Mar 22, 2024 · 13 comments
Open
3 tasks

24PI2 Planning #2799

JillieBeanSim opened this issue Mar 22, 2024 · 13 comments
Assignees
Labels
Milestone

Comments

@JillieBeanSim
Copy link
Contributor

JillieBeanSim commented Mar 22, 2024

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

24Q2 Plan Objectives

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

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

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

CICS Related Issues (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

  1. 2 of 16
    Epic bug
  2. 1 of 3
    Epic enhancement
  3. 3 of 13
    Epic enhancement v3
    JillieBeanSim
@JillieBeanSim
Copy link
Contributor Author

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
Copy link
Contributor

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

@JillieBeanSim
Copy link
Contributor Author

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

@JillieBeanSim
Copy link
Contributor Author

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

@JillieBeanSim
Copy link
Contributor Author

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

@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
Copy link
Contributor

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

@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.

@JillieBeanSim JillieBeanSim added this to the 24PI2 milestone Apr 11, 2024
@adam-wolfe
Copy link
Contributor

I think we will also want to include #2322

@JillieBeanSim
Copy link
Contributor Author

added @adam-wolfe
also updated community ZE planning page

@zFernand0
Copy link
Member

zFernand0 commented Apr 12, 2024

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:

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

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

@adam-wolfe
Copy link
Contributor

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

@adam-wolfe
Copy link
Contributor

adam-wolfe commented Apr 24, 2024

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
Copy link
Contributor Author

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
Copy link
Contributor

Sounds good to me 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: PI Backlog
Development

No branches or pull requests

3 participants