Skip to content

Update CIs links on release-process docs #6674

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,11 @@
2. Package two days before a release. So if the release is to be on Thursday,
package on Tuesday. Think about timezones as well.

3. Ensure that the tests on Travis CI are green.
3. Ensure that the tests on CIs are okay. See:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
3. Ensure that the tests on CIs are okay. See:
3. Ensure that the tests on CIs are working. See:

or

Suggested change
3. Ensure that the tests on CIs are okay. See:
3. Ensure that the tests on CIs are succeeding. See:

are also options here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "okay" is fine.


See: https://travis-ci.org/php/php-src/builds
* https://travis-ci.com/github/php/php-src
* https://ci.appveyor.com/project/php/php-src
* https://dev.azure.com/phpazuredevops/PHP/_build

It is recommended to do so a couple of days before the packaging day, to
have enough time to investigate failures, communicate with the authors and
Expand Down