Lines Matching +full:bump +full:- +full:version

5 …-part version number (`vX.Y.Z`) and follow [semantic versioning](https://semver.org/), which defin…
6 - **Major version bumps** only happen on rare occasions. In order to qualify for a major version bu…
7 - **Minor version bumps** happen approx. every 6 weeks as part of the normal release cycle as defin…
8 - **Patch version bump** corresponds to bugfixes done on release branch.
11 - A **minor** version will not necessarily add new functionality. This follows from the fact that w…
12 - Backward compatibility can be broken by a **minor** release if the API affected by the change was…
15 - New implementations start at v0.x.y version and until they reach 1.0, they are considered not rea…
16 - The "1.0" release has semantics of GA (generally available) and being production ready. Requireme…
17   - basic RPC features are feature complete and tested
18   - implementation is tested for interoperability with other languages
19   - Public API is declared stable
20 - Once a gRPC library reaches 1.0 (or higher version), the normal rules for versioning apply.
22 ## Policy for updating the major version number
24 …version (all languages follow the same release schedule). Nevertheless, because we also strictly f…
26 ### Situations when it's ok to do a major version bump
27 - **change forced by the language ecosystem:** when the language itself or its standard libraries t…
28 - **voluntary change:** Even in non-forced situations, there might be circumstances in which a brea…
30 …- fixing a security problem which requires changes to API (need to consider the non-breaking alter…
31 …- the change leads to very significant gains to security, usability or development velocity. These…
34 …- Description of the proposal including an explanation why the proposed change is one of the very …
35 …- Migration costs (= what does it mean for the users to migrate to the new API, what are the costs…
36   - Pros of the change (what is gained and how)
37 …- Cons of the change (e.g. user confusion, lost users and user trust, work needed, added maintenan…
38 …- Plan for supporting users still using the old major version (in case migration to the new major …
40 …version bump allows changing APIs used by the users, it must not impact the interoperability of th…
42 ### Situations that DON'T warrant a major version bump
43 - Because other languages do so. This is not a good enough reason because
44 …version bump has high potential for disturbing and confusing the users of that language and fragme…
45 - "I don't like this API": In retrospect, some API decisions made in the past necessarily turn out …