osdn migration: Time to start having at least "wrapper" ticket in osdn
Especially once 3.3 development begins, all issues must have osdn ticket, so that when NEWS for 3.3 is being collected (maybe winter 2026 - 2027), there's no need to check hrm (except maybe for additional info) and no need to put any hrm references to the NEWS.
This is now enforced.
We've soon been on osdn for two years. Time to remove people to follow also hrm for patches needing review? That is; I propose that now on there's at least "wrapper" ticket on osdn for anything entering review period. It can simply point to hrm ticket, and most of the handling of those old hrm tickets can still happen on hrm, but osdn-side ticket state must accurately tell the review -state. This will also make future osdn statistics more accurate, as then changes going through hrm are counted too.
(As this is just a proposal at this point, basically entering review period itself, do not assume that it's already in effect as binding all maintainers - though I myself start making such wrapper tickets immediately)