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

Correctly template spec.type and spec.lifecycle in copier-template.yaml #181

Closed
garryod opened this issue Aug 8, 2024 · 2 comments · Fixed by #187
Closed

Correctly template spec.type and spec.lifecycle in copier-template.yaml #181

garryod opened this issue Aug 8, 2024 · 2 comments · Fixed by #187
Assignees
Labels
bug Something isn't working

Comments

@garryod
Copy link
Member

garryod commented Aug 8, 2024

There are currently 32 components erroneously marked with spec.type=documentation and spec.lifecycle=experimental in the developer portal, the vast majority of which originated from this template. Please could you update the template such that these fields must be specified. Additionally, it would be good to remove sscc as the default for owner as it has been used in 22 of the 32 aforementioned repos

@garryod garryod added the bug Something isn't working label Aug 8, 2024
@garryod garryod self-assigned this Aug 8, 2024
@callumforrester
Copy link
Contributor

Looking at this now...

I agree that spec.type=documentation is erroneous, but I'm inclined to say that spec.lifecycle=experimental is a reasonable default value for new projects. Of the list you linked, I would consider almost all of the components that come from this template to be experimental, some may be arguably alpha. I may have misunderstood the classification though, open to other views.

@GDYendell
Copy link
Contributor

I agree most projects will start as experimental, but if it is a copier question then people will (might) read it when they update to the latest version and consider changing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants