Few would disagree with you. This is a classic resource problem, we need more volunteers and contributers 
edit: Don’t forget all customizations are a user responsibility, moreover regardless whether your software is proprietary or open source, the rule is caveat emptor!
Hi @clarkej
normally I would have agreed with you but definitely not for a major release like this. You shouldn’t put out release notes and steps to update for a major release without at least a clear warning that Custom Scripts and Workflows won’t work… that’s quite serious and will undoubtedly lead to some very nasty user experiences!
If we can save people some serious headaches then we should, rather than say “Sorry, it’s your responsibility to ensure everything works” - even if it is 
Cheers
“at least a clear warning that Custom Scripts and Workflows won’t work… that’s quite serious and will undoubtedly lead to some very nasty user experiences!”
Ok yes perhaps a sentence or two of warning or say a disclaimer.
The question is, what is obvious and what to assume about the user - where do you draw the line?
Naivete and due diligence go hand in hand and usually resolve themselves in short order.
Caveat emptor means you may need to pay someone to blame 
I totally agree… we don’t matter to catch-up with changes on how things work (is part of the growth process), but lack of information makes it impossible to contribute. We’ll remain in V10 until Custom Scripts are back , since our project relies on it. All the best for the magnificent work !
Well that’s the basis of this forum, for folks to inform themselves assuming they are motivated!?
EDIT: Perhaps best to close this thread now…