6 ms·

In general, if I understand correctly, "Release candidate" implies "unstable." The emphasis is on "Candidate," not "Release," i.e. "This bundle could end up bei

In general, if I understand correctly, "Release candidate" implies "unstable." The emphasis is on "Candidate," not "Release," i.e. "This bundle could end up being the final version, but it probably won't."

ygra 10y ago
It tends to imply that the API is stable, though. RCs tend to get a few bug fixes and other polishing, but not complete API overhauls.
fabian2k 10y ago
The old definition I learned is that it is a version that you think could be released, unless any major bugs appear that you don't know about yet. It's not something where you would expect major API changes. But those definitions have become much more fluid, and it's hard to find out which definitions everyone is using.
kevindong 10y ago
To me personally, "release candidate" implies "almost ready". After all, it is a candidate for release. In other words, it's released to the public for some final testing and bug fixes with no chance of additional features, API changes, etc. between the RC and the final release.
tomnipotent 10y ago
RC absolutely means non-breaking API changes. Bug fixes yes, but the API will be stable.
- dragonwriter 10y ago
  It does not "absolutely" mean that. It certainly means API changes are not anticipated, and that there should be a very significant problem with an API to lead to an API change at that point; certainly one would hope that fundamental flaws in an API that make it unsuitable for release would be identified well before an RC. But its certainly possible to have reasons to make a breaking change from an RC (e.g. -- not necessarily relevant to a front-end framework, obviously -- a security vulnerability uncovered that reveals a critical flaw in the logical design, rather than implementation, of an API.)
  - Udik 10y ago
    > its certainly possible to have reasons to make a breaking change from an RC Sure. After which you issue a new RC, not the final release.
jakub_g 10y ago
"Release candidate" != "Release" but in my understanding "RC" is "almost finished, but we might have some bugs to fix before" Anyway my personal attitude is to keep away from alphas, betas, RCs and stable-from-yesterday. Applies to frameworks, operating systems and virtually everything, and each time I don't follow that rule, I regret.

ygra 10y ago

It tends to imply that the API is stable, though. RCs tend to get a few bug fixes and other polishing, but not complete API overhauls.

fabian2k 10y ago

The old definition I learned is that it is a version that you think could be released, unless any major bugs appear that you don't know about yet. It's not something where you would expect major API changes. But those definitions have become much more fluid, and it's hard to find out which definitions everyone is using.

kevindong 10y ago

To me personally, "release candidate" implies "almost ready". After all, it is a candidate for release. In other words, it's released to the public for some final testing and bug fixes with no chance of additional features, API changes, etc. between the RC and the final release.

tomnipotent 10y ago

RC absolutely means non-breaking API changes. Bug fixes yes, but the API will be stable.

dragonwriter 10y ago
It does not "absolutely" mean that. It certainly means API changes are not anticipated, and that there should be a very significant problem with an API to lead to an API change at that point; certainly one would hope that fundamental flaws in an API that make it unsuitable for release would be identified well before an RC. But its certainly possible to have reasons to make a breaking change from an RC (e.g. -- not necessarily relevant to a front-end framework, obviously -- a security vulnerability uncovered that reveals a critical flaw in the logical design, rather than implementation, of an API.)
- Udik 10y ago
  > its certainly possible to have reasons to make a breaking change from an RC Sure. After which you issue a new RC, not the final release.

jakub_g 10y ago

"Release candidate" != "Release" but in my understanding "RC" is "almost finished, but we might have some bugs to fix before" Anyway my personal attitude is to keep away from alphas, betas, RCs and stable-from-yesterday. Applies to frameworks, operating systems and virtually everything, and each time I don't follow that rule, I regret.