On Jan 9, 2014, at 16:35 , sky5w...@gmail.com wrote: > Took time to reply, cause I had to clean the coffee I spit up! > A released application should be considered stable and a conservative view > would say its libs should not contain alphas or betas. > The ease of compiling a bleeding edge Fossil.exe is already in place for > those wishing to gain the latest features in trunk.
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. SQLite QA is so impressive that some may be pretty comfortable with having any version, provided it has passed a full test suite, included in their systems. The problem here is the message sent by the word "alpha". What it usually means is "I just wrote it, hope it will not explode in your face, but no warranties". Therefore if we want to say "Fossil is rock-solid", we can't say "it uses alpha libs", just to avoid the confusion, no matter the actual quality. Kind regards, Remigiusz Modrzejewski _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
