...

Text file src/sigs.k8s.io/structured-merge-diff/v4/RELEASE.md

Documentation: sigs.k8s.io/structured-merge-diff/v4

     1# Release Process
     2
     3This repo will follow go library versioning semantics.
     4
     5Currently, it is not stable (version 0.0.0) and interfaces may change without
     6warning.
     7
     8Once it looks like this code will be used in a Kubernetes release, we will mark
     9it v1.0.0 and any interface changes will begin accumulating in a v2 candidate.
    10
    11We will publish versions in a way that's conformant with the new "go modules".
    12
    13Reviewers / owners are expected to be vigilant about preventing
    14interface-breaking changes in stable versions.
    15
    16When a candidate version is ready to be promoted to stable, the process is as follows:
    17
    181. An issue is proposing a new release with a changelog since the last release
    191. All [OWNERS](OWNERS) must LGTM this release
    201. An OWNER changes the name from vX-candidate to vX and starts a v(X+1)-candidate directory/module (details TBD when we first do this)
    211. The release issue is closed
    221. An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
    23
    24(This process is currently intended to be a hint and will be refined once we declare our first stable release.)

View as plain text