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

Updates in the Release Notes for Zowe Application Framework #4180

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

ArooshLele
Copy link
Collaborator

The following updates:

Enhancements for:
-Zlux App Server package
-Zowe Installer

Bug Fixes for:
-Zlux App Server package
-Zowe Installer

Describe your pull request here:

List the file(s) included in this PR:

After creating the PR, follow the instructions in the comments.

The following updates:

Enhancements for:
-Zlux App Server package
-Zowe Installer

Bug Fixes for:
-Zlux App Server package
-Zowe Installer
@ArooshLele ArooshLele added release: V3 Zowe V3 content review: doc Needs review by Doc Squad member review: sme Needs review by an SME area: Zowe App Framework Related to the Zowe Application Framework labels Feb 12, 2025
Copy link

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

  • Add the label review: doc.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
  • Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

1 similar comment
Copy link

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

  • Add the label review: doc.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
  • Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

Copy link

📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

2 similar comments
Copy link

📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

Copy link

📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

@ArooshLele ArooshLele requested a review from janan07 February 12, 2025 12:21
Copy link

github-actions bot commented Feb 12, 2025

@github-actions github-actions bot temporarily deployed to pull request February 12, 2025 12:26 Inactive
Copy link
Collaborator

@janan07 janan07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please run this content through a spell checker. Also, the links should reference the issue which was created to address them, not the pull request that follows.

@github-actions github-actions bot temporarily deployed to pull request February 13, 2025 15:58 Inactive
@github-actions github-actions bot temporarily deployed to pull request February 19, 2025 10:41 Inactive
@github-actions github-actions bot temporarily deployed to pull request February 19, 2025 11:03 Inactive
@github-actions github-actions bot temporarily deployed to pull request February 21, 2025 10:23 Inactive
@1000TurquoisePogs
Copy link
Member

1000TurquoisePogs commented Feb 21, 2025

@janan07 At least for the webui squad, we have rarely if ever used issue numbers in changelogs. All these numbers are PR numbers. It is not uncommon for there to be no associated issue ticket. If you wish us to provide no number at all that is also possible.

@github-actions github-actions bot temporarily deployed to pull request February 24, 2025 10:29 Inactive
@github-actions github-actions bot temporarily deployed to pull request February 24, 2025 10:39 Inactive
@github-actions github-actions bot temporarily deployed to pull request February 24, 2025 11:42 Inactive

#### Zlux App Server package

* The app-server no longer causes Zowe to display "FSUM7422 node is not found" and "Node found in NODE_HOME" after starting Zowe. This avoids confusion about if node requirements are met.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue number?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@janan07 Yes, wherever the issue number was available in the Change log files, I mentioned the same issue number in the related markdown file. However, as discussed with Sean, if issue number was not available, the PR number was written instead of the issue number.

* The app-server no longer causes Zowe to display "FSUM7422 node is not found" and "Node found in NODE_HOME" after starting Zowe. This avoids confusion about if node requirements are met.

#### Zlux Server Framework
* App-server could not register with discovery server when AT-TLS was enabled for app-server.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue number?

* App-server could not register with discovery server when AT-TLS was enabled for app-server.

#### Zowe Common C
* Removed `ByteOutputStream` debug message, which was a part of the zwe command output.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue number?

* App-server tries to detect ssh and telnet ports (used by terminals) automatically. ([#292](https://github.com/zowe/zowe-install-packaging/issues/292))

#### Zowe Common C
* Module registry.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide a full sentence and a corresponding issue number?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@janan07 Although the issue number is available, the entry is rather code-specific and need not be mentioned on the What's New page. As discussed with Sean, the bullet for Module registry is removed.

* Module registry.

#### ZSS package
* Module registry.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide a full sentence and a corresponding issue number?

#### Zowe Common C
* Removed `ByteOutputStream` debug message, which was a part of the zwe command output.
* `HEAPPOOLS` and `HEAPPOOLS64` no longer need to be set to `OFF` for `configmgr`.
module registry
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is "module registry"?

Zowe Common C and ZSS package both contained the term Module registry as the only bullet point.
Both (Zowe Common C and ZSS package) have been removed.
@github-actions github-actions bot temporarily deployed to pull request February 28, 2025 16:33 Inactive
As discussed with @1000TurquoisePogs , I mentioned the PR numbers instead of issue numbers if the issue numbers were unavailable.
@github-actions github-actions bot temporarily deployed to pull request February 28, 2025 17:25 Inactive
@github-actions github-actions bot temporarily deployed to pull request March 3, 2025 14:34 Inactive
-Added the missing pull request numbers for two bullets under the Zowe Common C title.
-Removed the bullet for module registry entry under the Zowe Common C title.
@github-actions github-actions bot temporarily deployed to pull request March 3, 2025 16:29 Inactive
@github-actions github-actions bot temporarily deployed to pull request March 10, 2025 15:46 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Zowe App Framework Related to the Zowe Application Framework release: V3 Zowe V3 content review: doc Needs review by Doc Squad member review: sme Needs review by an SME
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants