The poll is still listed as closed on that page. I think you forgot to update the voting widget to have a different question. (That's the unique ID used by the wiki.)
After a cool-down period, I am announcing to reopen the vote of the RFC 'Add Form Feed in Trim Functions'
The cooldown period after canceling a vote is 14 days, which have not yet expired. I also believe you might have missed the “target version” discussion, at least you didn't reply there.
The RFC still states PHP 9.0 as the target version. As I mentioned in the other voting thread, I believe this to be a bad choice. I will vote no if the RFC is targeting PHP 9.0, I will (and did under the assumption that PHP 8.5 meant 8.6) vote yes if the RFC is targeting PHP 8.6.
After a cool-down period, I am announcing to reopen the vote of the RFC 'Add Form Feed in Trim Functions'
The cooldown period after canceling a vote is 14 days, which have not
yet expired. I also believe you might have missed the “target version”
discussion, at least you didn't reply there.
The RFC still states PHP 9.0 as the target version. As I mentioned in
the other voting thread, I believe this to be a bad choice. I will vote
no if the RFC is targeting PHP 9.0, I will (and did under the assumption
that PHP 8.5 meant 8.6) vote yes if the RFC is targeting PHP 8.6.
Hi Weilin,
Thank you for your work on this RFC.
I would also prefer that this change target PHP 8.6. The BC break is extremely minor,
more along the lines of a bugfix that makes the trim functions work as expected.
If every improvement with a tiny BC break is deferred to the next major release,
there becomes less reason to upgrade to minor releases, and then when a new major
version comes out and all the small BC breaks have to be dealt with at once the
upgrade is much more daunting. Spreading fixes/improvements with slight BC breaks
across minor releases makes staying up-to-date easier overall and more valuable.