Commit 163d2d1
timers: unlock the timers API
Change the Stability Index on timers from Locked to Stable.
Note that this is not intended to encourage changes to the timers API,
but to allow it when its useful for Node.js (as has happened in
violation of the documented stability level), and possibly to simplify
the stability levels by removing Locked altogether.
PR-URL: #11580
Ref: #11200
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent cdee945 commit 163d2d1
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,6 +1,6 @@ | |||
| 1 | 1 | # Timers | |
| 2 | 2 | ||
| 3 | - > Stability: 3 - Locked | ||
| 3 | + > Stability: 2 - Stable | ||
| 4 | 4 | ||
| 5 | 5 | The `timer` module exposes a global API for scheduling functions to | |
| 6 | 6 | be called at some future period of time. Because the timer functions are | |
0 commit comments