A short summary of that discussion, to use @brian's words, is
I agree. Testing is important; testing is an investment (as @brian wrote):
I agree with that, too.
My question is simple: where is the J! 4 testing team?
In addition, I would also ask, what is OSM's investment in backing a J! 4 testing team? Does a team exist? What are the qualifications needed for people to join this team? Who is the team leader? What is the purpose of such a team? How do I and others join this team? How often does the team meet? How do team members collaborate with and report back to other team members about their testing activities?
What has occurred in the four months since @brian wrote what he did on the forum? Has his advice converted into action?
So, while I agree with the need for people to test J! 4 so that we can move past the alpha phase and into beta and beyond, how should we go about these tasks? I don't propose that OSM should create a testing team/working group as an official part of the organisation but I don't see any discussion from departmental reports to get this activity off the ground. Can someone please point me to where this activity is discussed and what pre-requisites are needed for people to get involved with testing J! 4, please?