Update CIs links on release-process docs #6674
Conversation
Couple of updates: - Travis CI is now on .com, no longer on .org - We also use AppVeyor and Azure, so let's list them - "CI are green" does not fit colorblinds, let's avoid it
carusogabriel
added
the
Category: Documentation
| @@ -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: | |||
There was a problem hiding this comment.
| 3. Ensure that the tests on CIs are okay. See: | |
| 3. Ensure that the tests on CIs are working. See: |
or
| 3. Ensure that the tests on CIs are okay. See: | |
| 3. Ensure that the tests on CIs are succeeding. See: |
are also options here.
|
You might want to specify that Travis CI is limited to PHP 7.3 (which is a security release). |
|
@Girgias Once this one is accepted, I'll go downstream and update the ones needed. RMs know where to look, but I think it's important to update the |
|
I think PHP-7.3 should be left alone with this; it may be okay for PHP-7.4, but I'm not sure whether release managers actually look at that; I use the one in master for a long time. Anyhow, just drop the mention of Travis; these builds are no longer working for several weeks now, and it's somewhat unlikely to find somebody to sponsor travis.com, besides that Azure Pipelines are working well for us. |
|
Fixed via #6829 |
Couple of updates: