But, for a project this size, the lack of unit testing is starting to hurt.
Why don't Tiny and the community organizes a "Test Sprint" where we would dedicate some effort writing unit tests for 5.0/5.2? Yes, they are boring but with that number of regressions, and not-so-frequent releases, I worry about next stable release quality.
If Tiny writes some nice testing guidelines, I'm confident that the community would jump in.
+1 for the merge.
But, for a project this size, the lack of unit testing is starting to hurt.
Why don't Tiny and the community organizes a "Test Sprint" where we would dedicate some effort writing unit tests for 5.0/5.2? Yes, they are boring but with that number of regressions, and not-so-frequent releases, I worry about next stable release quality.
If Tiny writes some nice testing guidelines, I'm confident that the community would jump in.