mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-17 15:50:10 +00:00
TODOs
This commit is contained in:
parent
d9b583e631
commit
64f456343c
@ -177,6 +177,8 @@ include everything in the release notes.
|
|||||||
|
|
||||||
## Origin of the Sources
|
## Origin of the Sources
|
||||||
|
|
||||||
|
TODO(ihmccreery) update this
|
||||||
|
|
||||||
Kubernetes may be built from either a git tree (using `hack/build-go.sh`) or
|
Kubernetes may be built from either a git tree (using `hack/build-go.sh`) or
|
||||||
from a tarball (using either `hack/build-go.sh` or `go install`) or directly by
|
from a tarball (using either `hack/build-go.sh` or `go install`) or directly by
|
||||||
the Go native build system (using `go get`).
|
the Go native build system (using `go get`).
|
||||||
@ -193,6 +195,8 @@ between releases (e.g. at some point in development between v0.3 and v0.4).
|
|||||||
|
|
||||||
## Version Number Format
|
## Version Number Format
|
||||||
|
|
||||||
|
TODO(ihmccreery) update this
|
||||||
|
|
||||||
In order to account for these use cases, there are some specific formats that
|
In order to account for these use cases, there are some specific formats that
|
||||||
may end up representing the Kubernetes version. Here are a few examples:
|
may end up representing the Kubernetes version. Here are a few examples:
|
||||||
|
|
||||||
@ -251,6 +255,8 @@ is the complete SHA1 of the (dirty) tree used at build time.
|
|||||||
|
|
||||||
## Release Notes
|
## Release Notes
|
||||||
|
|
||||||
|
TODO(ihmccreery) update this
|
||||||
|
|
||||||
No official release should be made final without properly matching release notes.
|
No official release should be made final without properly matching release notes.
|
||||||
|
|
||||||
There should be made available, per release, a small summary, preamble, of the
|
There should be made available, per release, a small summary, preamble, of the
|
||||||
|
Loading…
Reference in New Issue
Block a user