What is the plan?

I know software is a tricky business (am in it myself), but I miss a communicated plan (like q4 2011). Given the todo list open has a lot of basic stuff yet, NOT only bugs, I would not say anything so far is RC level... (more: beta). THat is ok.

I just wonder when we can expect v5 to get availability.

Why are they calling the builds RC (RELEASE Candidate) if there are so many things left to do.

A release candidate, by definition, is something that is going to be the next release unless additional bugs are found. But if there are known things missing, not just bugs, then calling it RC anything is inaccurate. Call it alpha or call it beta, but don't call it RC unless it is ready for release and just checking for additional bugs.

MT's response will be what it's always been: When it's ready

Just dont mistake ROS 5.0 RTM as being stable, History tells us from ROS 3&4 that stability for production networks comes around ROS x.4-10, For out main network of 1000+ devices we'd only really moved to ROS 3 after 3.20-3.22, Even then the main network deployment was 3.30 which stayed that way until ROS 4.10 which we have stuck with due to issues with 4.13+

As always the trick with any MT release is to wait 24-48 hours for any show stopping bugs, test in lab, deploy to small section of network, wait 1-2 weeks, deploy everywhere

Just dont mistake ROS 5.0 RTM as being stable, History tells us from ROS 3&4 that stability for production networks comes around ROS x.4-10, For out main network of 1000+ devices we'd only really moved to ROS 3 after 3.20-3.22, Even then the main network deployment was 3.30 which stayed that way until ROS 4.10 which we have stuck with due to issues with 4.13+

for now our plan is to stay at least for v5.10 to upgrade . let's see what's happening later .