02-19-2021, 02:47 PM
(This post was last modified: 02-19-2021, 02:48 PM by TheOldPresbyope.
Edit Reason: typo
)
It's exciting to see all the interest in the CamillaDSP but I'm getting concerned that folks are misunderstanding what the test team and the test releases are all about.
[what follows is my idiosyncratic view of the life of a tester]
Each TR is a packaging of the code in the current develop branch of the moOde repo. This code is in constant flux. It's up to the test team members to push all the buttons, twist all the knobs, and hammer on all the interfaces in an attempt to break the TR.
Testing results are funneled back in the Test Team Forum (and/or the issues log in the github repo) and are used by team members as they edit and extend the code. The Test Team Forum is closed not for secrecy or privacy but to spare the larger community from all the chatter during the sausage-making activity
When we get to a TR we can't easily break and we agree that remaining issues can wait 'til later, Tim captures the current state of the develop branch as an official release. Then the cycle repeats.
Why do I say all this? Because those of you asking for early access to the TRs have to accept that
Regards,
Kent
[what follows is my idiosyncratic view of the life of a tester]
Each TR is a packaging of the code in the current develop branch of the moOde repo. This code is in constant flux. It's up to the test team members to push all the buttons, twist all the knobs, and hammer on all the interfaces in an attempt to break the TR.
Testing results are funneled back in the Test Team Forum (and/or the issues log in the github repo) and are used by team members as they edit and extend the code. The Test Team Forum is closed not for secrecy or privacy but to spare the larger community from all the chatter during the sausage-making activity
When we get to a TR we can't easily break and we agree that remaining issues can wait 'til later, Tim captures the current state of the develop branch as an official release. Then the cycle repeats.
Why do I say all this? Because those of you asking for early access to the TRs have to accept that
- there's no expectation that the code will work the way you want and won't break in ways you don't, and
- there is an expectation that you to report your findings back to the test team for the benefit of the entire moOde community
Regards,
Kent