rfc:release-md5-deprecation

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
rfc:release-md5-deprecation [2017/06/13 23:33] – Swap order pollitarfc:release-md5-deprecation [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 3: Line 3:
   * Date: 2017-05-30   * Date: 2017-05-30
   * Author: Sara Golemon <pollita@php.net>   * Author: Sara Golemon <pollita@php.net>
-  * Status: Under Discussion+  * Status: Accepted
   * First Published at: http://wiki.php.net/rfc/release-md5-deprecation   * First Published at: http://wiki.php.net/rfc/release-md5-deprecation
  
Line 26: Line 26:
 All votes have50%+1 Majority required to pass: All votes have50%+1 Majority required to pass:
  
-<doodle title="Should MD5 checksums be left in or removed?" auth="pollita" voteType="single" closed="false">+<doodle title="Should MD5 checksums be left in or removed?" auth="pollita" voteType="single" closed="true">
    * Remove    * Remove
    * Keep    * Keep
Line 35: Line 35:
 Assuming the above yields "Remove", the following question determines if we should "**remove**" the hashes immediately, or "**deprecate**" them for a period of one year prior to removal. Assuming the above yields "Remove", the following question determines if we should "**remove**" the hashes immediately, or "**deprecate**" them for a period of one year prior to removal.
  
-<doodle title="Remove immediately or deprecate prior to removal?" auth="pollita" voteType="single" closed="false">+<doodle title="Remove immediately or deprecate prior to removal?" auth="pollita" voteType="single" closed="true">
    * Remove Now    * Remove Now
    * Deprecate    * Deprecate
rfc/release-md5-deprecation.1497396793.txt.gz · Last modified: 2017/09/22 13:28 (external edit)