Am 09.01.2014 17:52, schrieb Remigiusz Modrzejewski:
You do realize that "alpha" and "beta" are just words? With different
quality assurance procedures in different projects, trying to use them
as a gauge of anything else than releaser intent is misleading.
Well, can I come in here?
Maybe alpha and beta are just words, but they are used for a reason. The
reason is, that the software in these states is not fully tested and not
to be considered stable. Therefore the software should not under any
circumstances be used in productive environment.
So please, if anyone is going to give a stable release, do not use alpha
or beta dependencies on it, because that makes your software alpha or
beta for a reason. There is nothing that tells me, if I'm using a stable
release of fossil, if my repository is getting fucked up by a feature
from the alpha/beta sqlite.
Maybe sqlite has a very very good QA and the software is extremly
stable, but even the own developers do not trust the version as stable -
so why should we?
regards,
Oliver
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
