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.

Sign up for GitHub

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

Jump to bottom

Define release guidelines for baremetal-operator and start publishing releases #404

Closed
2 tasks
Arvinderpal opened this issue Jan 23, 2020 · 4 comments
Closed
2 tasks

Define release guidelines for baremetal-operator and start publishing releases #404

Arvinderpal opened this issue Jan 23, 2020 · 4 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@Arvinderpal
Copy link

Arvinderpal commented Jan 23, 2020 •
edited

We should adopt a releasing approach similar to that of CAPI and follow the well-known semantic versioning guidelines (see references below).

Besides this being a good practice, integration with the redesigned clusterctl will require that projects follow the above mentioned releasing strategy. A similar issue was created for capbm: metal3-io/cluster-api-provider-baremetal#224

PR Tracking:
@dhellmann
Copy link
Member

We generally put project-wide docs like that in the metal3-docs repository. Maybe we could do that for these release policies and instructions?

Arvinderpal added a commit to Nordix/baremetal-operator that referenced this issue Jan 23, 2020
@Arvinderpal
Makefile support for:
7cdbf71 
 * Docker build and push commands that align with CAPI model.
 * Release manifests generation.

Issue:
metal3-io#404
@Arvinderpal Arvinderpal mentioned this issue Jan 23, 2020
Closed
@stbenjam
Copy link
Member

Could you move this issue to metal3-docs? Any metal3-wide docs should go there, including defining our release processes.

/kind documentation

/close

@metal3-io-bot metal3-io-bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jan 29, 2020
@metal3-io-bot
Copy link
Contributor

@stbenjam: Closing this issue.

In response to this:

Could you move this issue to metal3-docs? Any metal3-wide docs should go there, including defining our release processes.

/kind documentation

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Arvinderpal
Copy link
Author

Could you move this issue to metal3-docs? Any metal3-wide docs should go there, including defining our release processes.

/kind documentation

/close

metal3-io/metal3-docs#71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dhellmann @stbenjam @Arvinderpal @metal3-io-bot