Lines Matching refs:level
17 publish patch-level releases every four weeks, with at least one release
18 candidate (RC) published two weeks before each patch-level release.
142 > After GA, you will create (and push) a new *patch-level version branch*
144 > release for PHP 8.2.8 RC1, you will create the `PHP-8.2.8` patch-level
152 > We will use the patch-level version branch to commit any critical bug or
155 > Then, from the patch-level version branch, you will create another
262 > Patch-level version branches (e.g. `PHP-8.1.7`) will also *always* have
274 git push upstream PHP-X.Y.Z # patch-level version branch (post-GA only)
459 1. Check out the *patch-level version branch* for the release
470 patch-level version branch for this release.
472 Commit these changes and push the patch-level version branch. Ensure
477 > patch-level version branch.
479 3. Run the `./scripts/dev/credits` script in the patch-level version branch,
487 4. Create a local-only release branch for this release from the *patch-level
499 the version numbers in the patch-level version branch should be
660 8.2. There is no need to provide the patch level.
771 > For standard patch-level releases, we will note "This is a bugfix release."
785 ## Re-releasing the same version or a patch-level (i.e., `-plN`)
798 and release a patch-level (i.e., *pl*) release. If it is not critical and/or
802 If you choose to create a patch-level release, follow these steps: