Lines Matching refs:RC
19 candidate (RC) published two weeks before each patch-level release.
32 We refer to alpha, beta, and RC as *non-stable releases*, while GA are *stable*.
101 ## Packaging a non-stable release (alpha/beta/RC)
103 All releases during the pre-release cycle (alpha/beta/RC) leading up to the GA
131 > During the first RC release, you will create (and push!) the version
188 > We update `Zend/zend.h` only when preparing RC and GA releases. We do not
248 For example, if the RC is `8.2.1RC1` then the version numbers in the version
250 build a new RC to make sure `version_compare()` works correctly. See
346 ## Announcing a non-stable release (alpha/beta/RC)
430 possible release date of either the next RC or the final release. Also
454 Derick) to post a tweet with the RC release announcement and link to the news
708 The array probably contains information about the RC released two weeks ago
710 it's time to remove the RC build from the QA website.
713 stop displaying the RC build on the QA website. You may also remove the
714 sha256 hashes for the RC tarballs, but it's not necessary. For an example,
737 * Does the RC for this version still appear on the QA home page?
846 When the new version has reached the first RC, it is time to create a new
888 > version ready for RC and GA. During this time, the main branch is *only* for
895 1. When you release the first pre-GA RC, remind the documentation team
