the problem is, they're going to make a ton of additional changes that span from bugfixes to feature changes _AFTER_ the beta test.
This is why everyone knows ED's beta test periods are a joke. The entire point is to test the product before release. You completely miss the entire point of a beta test when you go and make additional changes after the final beta test.
Actually, I'm going to give them some points for how they're handling this release. Normally they have a Beta, it finishes, and 3 days - week later it goes live, often without any of the things fixed that were discovered to be broken in the Beta. This time we had a Beta, it's done, and now they're working on polishing it up based on the feedback/testing. So that is an improvement.
A bigger improvement would have been to not shut the Beta down, at least not completely. Maybe shut it down for a week or two while they put major changes in, then bring it back up again for us to continue testing, see if it all (or mostly checks out) and then release it to live.
Personally, I'm conflicted on this release - normally I would want them to take as much time as they need to polish it up. But in this case, I'm very, VERY eager for the new mat/data inventory system. Also going through Chieftain withdrawal...
Still, I'd say the way they are handling this release is better than what they did with 2.1, 2.2, 2.3, and 2.4.