Lines Matching refs:it
123 > branch from the main branch. Do not push it!
317 Or you may go to https://gist.github.com to create it manually.
327 > If you do not have a `public_html` directory, create it and set its
376 you run it, it will ask several questions (see below). For pre-GA non-stable
391 # To end it, hit <enter>.<enter>
423 > > Please DO NOT use this version in production, it is an early test version.
474 > candidate for this version. If it is for a PHP-X.Y.0 version, then just
477 2. If a CVE commit needs to be merged to the release, have it committed to
479 to 7.2, merge to 7.3, 7.4, etc.). Then, you can cherry-pick it into the
493 > It's very rare this will make changes at this point, but we run it here
590 Or you may go to https://gist.github.com to create it manually.
698 Within these files, it will generate standard messages for the new version.
731 it's time to remove the RC build from the QA website.
735 sha256 hashes for the RC tarballs, but it's not necessary. For an example,
761 Keep in mind it may take up to an hour for the websites to sync.
782 > If it is a security release, we must note "This is a security release."
808 and release a patch-level (i.e., *pl*) release. If it is not critical and/or
825 highlight the major important things (security fixes) and when it is
847 Specifically, it occurs when the first beta release is packaged, which means the
867 When the new version has reached the first RC, it is time to create a new
919 link to it in the release announcements.