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

[FEATURE] Provide a Spec guideline for CRs for moving to v1beta1 #1377

Open
1 task done
qu1queee opened this issue Sep 6, 2023 · 2 comments
Open
1 task done

[FEATURE] Provide a Spec guideline for CRs for moving to v1beta1 #1377

qu1queee opened this issue Sep 6, 2023 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@qu1queee
Copy link
Contributor

qu1queee commented Sep 6, 2023

Is there an existing feature request for this?

  • I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

We need to document in a table, how can a user move out their CRs from v1alpha1 to v1beta1. Here I mainly refer to the spec paths. Similar to what I see https://tekton.dev/docs/pipelines/migrating-v1beta1-to-v1/

Describe the solution that you would like.

A markdown file containing helpful information for anyone to modify their v1alpha1 CR into a v1beta1

Describe alternatives you have considered.

None

Anything else?

Applies to Builds, Buildruns

@qu1queee qu1queee added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 6, 2023
@qu1queee qu1queee added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 20, 2023
@qu1queee
Copy link
Contributor Author

From Refinement. We need to transfer part of https://shipwright.io/blog/2023/11/07/introducing-shipwright-beta-api/ into our docs in Shipwright/Build

@qu1queee qu1queee added the documentation Improvements or additions to documentation label Jan 11, 2024
@qu1queee qu1queee added this to the release-v0.13.0 milestone Jan 11, 2024
@qu1queee qu1queee self-assigned this Feb 8, 2024
@qu1queee
Copy link
Contributor Author

qu1queee commented May 16, 2024

From Refinement, this still required, @qu1queee to finish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Todo
Development

No branches or pull requests

2 participants