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

Remove restriction on publishing new versions during code freeze #270

Closed
t1m0thyj opened this issue Jun 17, 2024 · 3 comments
Closed

Remove restriction on publishing new versions during code freeze #270

t1m0thyj opened this issue Jun 17, 2024 · 3 comments
Labels

Comments

@t1m0thyj
Copy link
Member

Is your feature or enhancement request related to a problem or limitation? Please describe

Sometimes during code freeze we want to publish a high-priority patch release but the workflows don't permit it.

Describe your enhancement idea

Remove the "staging mode" described in the readme:

When a Zowe release has been staged but is not yet GA, it is expected that the Zowe bundle version hosted on zowe.org and the version defined in zowe-versions.yaml@master will differ. During this period, the workflow runs in "staging mode"

Describe alternatives you've considered

Running the workflows with the FORCE_PUBLISH flag enabled, but this has to be done for each individual package.

Provide any additional context

Consider whether we want to remove the "staging mode" check for all publishes or just for the @latest tag.

@t1m0thyj t1m0thyj added the enhancement New feature or request label Jun 17, 2024
@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad Jun 17, 2024
Copy link

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe CLI Squad Jun 19, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the Stale label Sep 17, 2024
Copy link

github-actions bot commented Oct 1, 2024

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
@github-project-automation github-project-automation bot moved this from Low Priority to Closed in Zowe CLI Squad Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Closed
Development

No branches or pull requests

2 participants