Have a list on what is planned on being imported to react from ST2

To put my "dev" hat on for a minute:

Realistically, a list of what's fixes/missing functionality is coming to React almost certainly doesn't exist (and "can't exist").

There will be a list of tickets with things like "Support TSR Smileys", "Provide Multiquote Functionality", "Support the {noparse} tag". Someone will assign priorities, and (in general) things get worked on according to their priority.

There will be some tickets assigned a "won't fix" priority - typically things where the "bug" is actually intended behaviour, or "we know fixing this would cause a bunch of other problems / be an insane amount of work".

But the normal way things "don't get fixed" is just that they are never high enough priority to get dealt with. They're on the system, TSR would like them to be fixed. But it just never actually happens.

The problem is that the priority system usually isn't accurate enough for even something vague like "the P1 stuff will happen, the P2 stuff might happen, the P3 stuff won't happen". I'm sure the original plan was (along the lines of) "When we deploy React, it will have multi-quote, images, bbcode edit mode". And then deadlines approached and a bunch of "must happen" stuff became "we'll do it later (maybe)". And conversely, something can be low priority and a developer has a thought "you know, I bet we could do that by doing XYZ", spends half an hour looking at it, and then it's done and ready for the next release.

Looking at what's been fixed (or hasn't) over the last two months, I expect an awful lot of missing functionality is going to fall in that "it's on the list, we have no idea when we'll get around to it" dead-zone.

I personally do not need or want a date (other community members might feel differently), just a list of what is coming or what’s not regardless of priority: https://docs.google.com/spreadsheets/d/1-VBsO9c3oSUzTs_S7eLKLyhLIOELjxMGsEd2DYdbwPU

I’ve attached a Spreadsheet for people to see what I’m talking about (and what I mean when I created this thread).

I would have thought the project plan for a major rebuild like this to include some indication of what functionality was planned to be replicated and what was being retired.

It might not be as detailed as “this list of BBCodes” or “these emojis” but a review of the current functionality and what would be in scope for rebuilding seems like a fairly standard starting point.

It might be that some of the lost functionality that has been raised since launch was missing from the plans or that the issues with page loading speed have bumped things down or off the list but I would be very worried if there wasn’t something plotting out the baseline before anyone started writing code.

What I'm saying is that without a timescale (or priority), I suspect there will be virtually nothing on the list that is "definitely not coming to React".

Everywhere I've ever worked, there's a huge number of tickets where we haven't said "we're not going to do this", but internally it's not a priority and it's very unlikely to happen. Something more important always has to be done first.

Clearly TSR is suffering heavily from "stuff that has to be done first", so I'd expect it to be much the same.