fyi i noticed the discussion about 3.10 branched off into Developer and Community Engagement update: September 2025 so I wasn't sure where to put my answer, but I decided to use this main thread
+1 for keeping the discussion here. On the other thread, Rory said (back at the end of September):
I saw the 3.10 milestone on GitHub, thank you for creating that. The only thing I’d like to add is the resolution to the drag and drop feature as discussed on #7345.
Do we still want to try and include drag-and-drop in this release? I don't think it's a huge lift, but it seems blocked on a UX design proposal.
We're getting to the time of year where the holidays are fast approaching and we're in danger of pushing into 2026 unless we start the beta process soon. There's nothing magical about the calendar year boundary, but it's a nice delimiter.
I think some of the other issues currently targeted for 3.10 can be pushed out, but we need to figure out how to manage the V.next planning process, so that we have a milestone to push them to.
As a straw horse, I'll propose the following:
- rename the 4.0 milestone to something more representative of its historical role such as 4.0-proto (or perhaps "delta" which I think the branch was renamed)
- create a new milestone called V.next for the next major release which doesn't have compatibility constraints
- move open issues which are still relevant from 4.0-proto to V.next (or the backlog, if longer term goals). Close non-relevant open issues.
- [the hard part] go through closed 4.0-proto issues and identify those which have been closed, but only merged to the 4.0/delta branch and not to master. Reopen these and move them to either V.next or the backlog.
Only the first two steps (choosing names, in particular) are needed to enable moving issues out of 3.10.
Tom