Next STD Stabilization Iteration Plan

[kt3k]

We're planning to stabilize the below items in STD in the next batch. What do you think?

Package

• @std/ini (now it supports number, boolean, and null types)

APIs

• uuid/unstable-v7 (new API, @std/uuid: Stabilize @std/uuid/v7 #6174)
• streams/unstable-to-lines (new API, better ergonomics for reading lines)
• text/unstable-to-constant-case (new API)
• async/unstable-mux-async-iterator (Addition of constructor)
• path/unstable-basename (Addition of file URL overload)
• path/unstable-dirname (Addition of file URL overload)
• path/unstable-extname (Addition of file URL overload)
• path/unstable-join (Addition of file URL overload)
• path/unstable-normalize (Addition of file URL overload)

Note: all unstable items in STD are listed here https://github.com/denoland/std-unstable-tracker/blob/main/README.md

[iuioiua]

What criteria are being met for these items being ready to be stabilized? Genuine question. IMO, loosely defined criteria for an item like "it hasn't had any reported bugs or undergone any changes in a while" or even "feels ready" are fine.

[kt3k]

even "feels ready" are fine

This probably describes it the best..

BTW I'm cancelling this plan for now as there's too little reaction to this from both the core team and the community.

I'll try to stabilize only uuid/v7 for now, which is explicitly asked by some users