rfc:travis_ci

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
rfc:travis_ci [2014/04/14 19:49] stasrfc:travis_ci [2014/04/25 07:45] stas
Line 30: Line 30:
 It is proposed that the main responsibility of keeping the CI tests green will rest with the RM of the particular branch, in case of version branch. One of the responsibilities is that the release should not be made unless the CI tests are green, and the RM is primarily responsible for bringing it to green in one of the ways described below.  It is proposed that the main responsibility of keeping the CI tests green will rest with the RM of the particular branch, in case of version branch. One of the responsibilities is that the release should not be made unless the CI tests are green, and the RM is primarily responsible for bringing it to green in one of the ways described below. 
  
 +We will also add instructions for the RM to README.RELEASE_NOTES on how to verify the release branch and ensure everything passes. 
 === Fixing tests === === Fixing tests ===
  
Line 53: Line 54:
 Proposed votes are as follows: Proposed votes are as follows:
  
-  - Accept the description in this RFC as an official policy of the PHP project with regard to the tests. +<doodle title="Accept the description in this RFC as an official policy of the PHP project with regard to the tests" auth="user" voteType="single"> 
-  Choose one or more of the four options above of handling bad commits, keeping in mind that choosing particular option would be the decision of the RM. +   * Yes 
 +   * No 
 +</doodle> 
 + 
 +Choose one or more of the four options above of handling bad commits, keeping in mind that choosing particular option would be the decision of the RM.  
 + 
 +<doodle title="Choose one or more of the four options above of handling bad commits" auth="user" voteType="multi"> 
 +   * Revert ASAP 
 +   * Revert after 1 week 
 +   * XFAIL 
 +   * Update test 
 +</doodle>
  
 The RFC will be considered accepted if over 50% vote for the acceptance, and any option having the vote of more than 50% of the voters will be considered approved. If none of the options get 50% acceptance but the first item will, the exact handling of the bad commits will be considered to be defined and in the meantime be the decision of the RMs.  The RFC will be considered accepted if over 50% vote for the acceptance, and any option having the vote of more than 50% of the voters will be considered approved. If none of the options get 50% acceptance but the first item will, the exact handling of the bad commits will be considered to be defined and in the meantime be the decision of the RMs. 
rfc/travis_ci.txt · Last modified: 2018/03/01 23:48 by carusogabriel