Comments (23)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
/remove-lifecycle stale
/lifecycle freeze
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
Stale issues close after 30d of inactivity. Reopen the issue with /reopen
. Mark the issue as fresh with /remove-lifecycle stale
.
/close
from metal3-docs.
@metal3-io-bot: Closing this issue.
In response to this:
Stale issues close after 30d of inactivity. Reopen the issue with
/reopen
. Mark the issue as fresh with/remove-lifecycle stale
./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.
from metal3-docs.
reopened, since this is still relevant
from metal3-docs.
Stale issues close after 30d of inactivity. Reopen the issue with /reopen
. Mark the issue as fresh with /remove-lifecycle stale
.
/close
from metal3-docs.
@metal3-io-bot: Closing this issue.
In response to this:
Stale issues close after 30d of inactivity. Reopen the issue with
/reopen
. Mark the issue as fresh with/remove-lifecycle stale
./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.
from metal3-docs.
Reopening, since this has not been solved yet and still relevant
from metal3-docs.
/triage accepted
from metal3-docs.
/remove-lifecycle stale
from metal3-docs.
Yesterday during the community meeting we discussed the process of starting Baremetal Operator project releases. We are going to follow the widespread semantic versioning scheme and since we have not yet announced BMO as stable we would like to have more frequent and smaller releases for now and when we reach the stability we would like to stick to the same release cycle as Kubernetes (3 times a year). But we will discuss it again when the time comes for that.
To start with, our MAJOR version will be 0, until we feel that the codebase is stable enough for the production. As such, we could start with MINOR version 0.1.0 and continue incrementing from there.
Main branch will be for development while release-MINOR.PATCH branch is for stable, tested and backwards compatible code. Whenever there is a new major or minor release, a new branch will be created with release-MINOR.PATCH name.
from metal3-docs.
@fmuyassarov major version 0 can be an issue for go.mod
Are we sure that that kind of release versioning will be compatible for go.mod usage?
from metal3-docs.
What is the issue? We have been using it in CAPM3 until now.
from metal3-docs.
What is the issue? We have been using it in CAPM3 until now.
https://go.dev/doc/modules/version-numbers
Hmm, you are correct as per the link above.
I assume possible issue can be with v0 to v1 (creating a branch or subfolder)
from metal3-docs.
What is the issue? We have been using it in CAPM3 until now.
https://go.dev/doc/modules/version-numbers
Hmm, you are correct as per the link above.
I assume possible issue can be with v0 to v1 (creating a branch or subfolder)
I don't see an issue in branching as well to be honest. But after your point, I realized that branch naming should not be release-MINOR.PATCH but instead release-MAJOR.MINOR because each MINOR can have 0,1,3..9 PATCH releases, and we don't want to create a branch for every single patch release. I will make correction on my email and thanks for pointing out.
from metal3-docs.
@fmuyassarov I was pointing out that go expects that new Major release should be in separate branch or subfolder and named as Major version value.
So transition for v0
to v1
, according to golang spec, we would need to put newer code in new branch named v1
or into subfolder v1
.
Not sure that this is actually needed for v0
to v1
, pretty much sure that this is needed for v1
to v2
transition.
from metal3-docs.
/remove-lifecycle stale
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
I would close this I think this issue has been resolved but please give your opinion.
from metal3-docs.
I would close this I think this issue has been resolved but please give your opinion.
+1
from metal3-docs.
We have started releasing BMO and we have a release guideline in review metal3-io/baremetal-operator#1170.
/close
from metal3-docs.
@Rozzii: Closing this issue.
In response to this:
We have started releasing BMO and we have a release guideline in review metal3-io/baremetal-operator#1170.
/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.
from metal3-docs.
Related Issues (20)
- User-guide: migrate BareMetalHost and HardwareData API docs from BMO HOT 4
- User-guide: migrate HostFirmwareSettings and FirmwareSchema API docs from BMO HOT 3
- User-guide: migrate configuration docs from BMO HOT 20
- A lot of broken links in metal3-docs HOT 48
- Baremetal guide is defaulting to no auth in Ironic HOT 5
- Document BMO e2e on real hardware HOT 6
- Pin ironic image for the quick-start HOT 2
- Bump Bare Metal Operator version in the quick-start HOT 3
- Feature: Add a resource to request the execution of a workload on a BareMetalHost HOT 13
- Go through the quick-start and fix/improve things you find HOT 4
- Document Metal3Cluster HOT 4
- Document Metal3Machine and Metal3MachineTemplate HOT 4
- Document Metal3Data and Metal3DataTemplate HOT 4
- Add cover pages for feature sections HOT 3
- Document IP reuse HOT 4
- Document user-data, meta-data and network-data usage with BareMetalHosts HOT 4
- Add API reference HOT 7
- Document unhealthy annotation HOT 4
- Running custom IPA in an environment where thereis no DHCP - preprovisioning image HOT 3
- Troubleshooting guide HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from metal3-docs.