Closed adam-wolfe closed 9 hours ago
Thank you for raising this enhancement request. The community has 90 days to vote on it. If the enhancement receives at least 10 upvotes, it is added to our development backlog. If it receives fewer votes, the issue is closed.
It looks like https://github.com/zowe/zowe-explorer-vscode/wiki/v3-Changes-for-Users-and-Extenders is already being used for this purpose.
Created a breaking changes document on Box: https://ibm.box.com/s/exray2epor6eh61ygvpe6urp3xb30rld
@adam-wolfe @JillieBeanSim Seems like we have 3 places for tracking V3 changes now, should we standardize on one going forward?
Hey @t1m0thyj our extenders are aware of the first 2 locations in our repo from our v3 webinars. Developers only have to worry about the Extenders.md and I have been transferring to the wiki page which also has a link to the live file in the repo for extenders to stay on top of the changes. The box document is new within the community, so I am not sure about that one in regards to Extenders awareness of it and access to it.
Discussed this at standup and I believe the plan is to keep the Box document up-to-date with any changes made to Extender.md, since all Zowe squads have been requested to create a Box document that details their V3 breaking changes 🙂
@adam-wolfe has opened a PR to add Box document link to zowe.org: https://github.com/zowe/zowe.github.io/pull/924
Is your feature request related to a problem? Please describe.
The Onboarding Squad has requested that all squads produce a list of breaking changes for V3. A document exists that covers breaking changes for Zowe CLI and the Client Node.js SDKs and is available here: https://ibm.box.com/s/9h18h0blwl0yrtxcyeh1i0am70vdlcs5 in the V3 folder on box: https://broadcom.ent.box.com/folder/228322599725
Describe the solution you'd like
The Zowe Explorer Squad should assemble something for Zowe Explorer and the Zowe Explorer APIs similar to what the CLI Squad has done.
Describe alternatives you've considered
Additional context