by Peke » Thu Mar 30, 2023 5:08 pm
TekGamer wrote: ↑Wed Mar 29, 2023 12:03 am
Isn't the point for some of us in the community that knowingly want to become part of the "Beta testers" group, is to help the dev team with testing unstable alpha/beta releases and report bugs?
Yes, when there is a public alpha/beta build. Occasionally when there is essential fix, we contact few users experiencing that issue and supply VERY unstable fix, which in 99.99% is not safe to be used for anything other than testing fix.
TekGamer wrote: ↑Wed Mar 29, 2023 12:03 am
I have been Gold lifetime license owner since since August 2007 and a loyal MediaMonkey user. I would never blame the dev team if I was running alpha or beta release (and accepting that risk)!
Simply said, unless build passes internal tests it will not be released to public. You maybe will not blame us, but there is many that would. Even we tell them 1000x times DO NOT PRESS RED BUTTON!!! Even I do not risk my personal Library during Night builds tests and I am obligated to press that RED BUTTON repeatedly so that you do not need to.
TekGamer wrote: ↑Wed Mar 29, 2023 12:03 am
I asked rusty to be added to the "Beta testers" group and never heard back. Wouldn't that be the purpose of a beta testers group, to assist in testing unstable alpha or beta releases?
There is no official Beta group you can join, access to non published versions is NDA/Need to know based and it was like that from Songs-DB (MediaMonkey v1.0) in 2002.
To be clear, there is no Beta build ATM, that screenshot is from Nightly Internal Developer Build, made directly from sources just to see if it starts and work. There is high regression risk updates in 5.1 ATM which are not for public, even it includes number of fixes that are low risk.
[quote=TekGamer post_id=507929 time=1680066184 user_id=8943]
Isn't the point for some of us in the community that knowingly want to become part of the "Beta testers" group, is to help the dev team with testing unstable alpha/beta releases and report bugs?
[/quote]Yes, when there is a public alpha/beta build. Occasionally when there is essential fix, we contact few users experiencing that issue and supply VERY unstable fix, which in 99.99% is not safe to be used for anything other than testing fix.
[quote=TekGamer post_id=507929 time=1680066184 user_id=8943]
I have been Gold lifetime license owner since since August 2007 and a loyal MediaMonkey user. I would never blame the dev team if I was running alpha or beta release (and accepting that risk)!
[/quote]Simply said, unless build passes internal tests it will not be released to public. You maybe will not blame us, but there is many that would. Even we tell them 1000x times DO NOT PRESS RED BUTTON!!! Even I do not risk my personal Library during Night builds tests and I am obligated to press that RED BUTTON repeatedly so that you do not need to.
[quote=TekGamer post_id=507929 time=1680066184 user_id=8943]
I asked rusty to be added to the "Beta testers" group and never heard back. Wouldn't that be the purpose of a beta testers group, to assist in testing unstable alpha or beta releases?[/quote]There is no official Beta group you can join, access to non published versions is NDA/Need to know based and it was like that from Songs-DB (MediaMonkey v1.0) in 2002.
To be clear, there is no Beta build ATM, that screenshot is from Nightly Internal Developer Build, made directly from sources just to see if it starts and work. There is high regression risk updates in 5.1 ATM which are not for public, even it includes number of fixes that are low risk.