Ubiquiti publicly rolls out UNMS Beta
-
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
-
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
-
Their website still shows the "Download Beta" link.
-
This challenges the "what does supported" mean, problem. It's like Ubuntu LTS and Ubuntu normal. Both get support. But one gets more support than the other. Not all support is equal. Typically, a beta will get support, but certainly not the level of support that production would get. The expectation is that support is expected to sometimes end with "well it just doesn't work." Whereas production support is expected to ensure that the device works, gets fixed, gets replaced, etc.
-
Along with every other page, that I'm clicking on about UNMS.
Probably just a slow web developer who hasn't gotten the required paperwork.
-
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
-
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
-
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
Expect <> free.
-
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
Expect <> free.
But free software has all the same release guidelines as commercial software. And MS products aren't normally free.
-
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
Expect <> free.
But free software has all the same release guidelines as commercial software. And MS products aren't normally free.
Again - what does cost have to do with anything?
As I also said - you'd all probably disagree with me.
-
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
Expect <> free.
But free software has all the same release guidelines as commercial software. And MS products aren't normally free.
Again - what does cost have to do with anything?
As I also said - you'd all probably disagree with me.
Because you mentioned it in the post I quoted.
-
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
Expect <> free.
But free software has all the same release guidelines as commercial software. And MS products aren't normally free.
Again - what does cost have to do with anything?
As I also said - you'd all probably disagree with me.
Because you mentioned it in the post I quoted.
Please highlight the part where I mentioned costs.
-
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti publicly rolls out UNMS Beta:
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
While I'm sure this has no baring in reality - for me release is a point but the public can get support for the thing.
That's not quite accurate. There is no reason that something unreleased can't offer support. How else do you really do your testing, get feedback, and so forth? It's an expectation that anything that the public can get would get some amount of support most likely, because otherwise, what is the purpose of the public nature of the testing?
Perhaps I should have added the words "expect to" to the support portion. As you said with the other thread, There should be no expectation of support for the product that was still in beta.
So, here is a question then, does Microsoft ever release software? Because nothing that MS makes comes with support.
What about Debian Linux, is it ever released?
Expect <> free.
But free software has all the same release guidelines as commercial software. And MS products aren't normally free.
Again - what does cost have to do with anything?
As I also said - you'd all probably disagree with me.
Because you mentioned it in the post I quoted.
Please highlight the part where I mentioned costs.
Same thing I quoted and you responded to.
