Skip to content

Commit d683a09

Browse files
authored
Add info about the release cycle to README.md (#17)
1 parent b1e2870 commit d683a09

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

README.md

+22
Original file line numberDiff line numberDiff line change
@@ -206,3 +206,25 @@ previously.
206206
- `7za` should be preferred over `unzip` and `zip` for compatibility reasons.
207207
- If you experience some strange crashes on MSYS2 tools, try the phpsdk_rebase_msys2 tool. MSYS2 tools might be have unstable
208208
on ASLR enabled systems.
209+
210+
# Internal notes
211+
212+
## Releases
213+
214+
Users of the PHP SDK are supposed to use tagged versions for stability and
215+
reproducability. This requires the maintainers of the PHP SDK to create such
216+
tags for *all* *relevant* *changes*. The tag format should be `php-sdk-X.Y.Z`,
217+
with the common major, minor and revision numbers.
218+
219+
Comprehensive changes, which would be hard to test extensively, such as updates
220+
to the bundled PHP or the MinGW tools, should walk through a QA (aka. pre-release)
221+
process, typically with beta versions (e.g. `php-sdk-X.Y.Zbeta1`). Only after
222+
these have been thoroughly tested, and all relevant issues have been resolved,
223+
a GA release should be tagged.
224+
225+
After each tag, a couple of other repositories should be informed about the
226+
available update, ideally in form of a pull request. These repositories are:
227+
228+
* https://github.com/php/php-src (for Windows CI)
229+
* https://github.com/php/php-windows-builder
230+
* https://github.com/php/setup-php-sdk

0 commit comments

Comments
 (0)