This project has moved and is read-only. For the latest updates, please go here.

Using 3.0 alpha in production

Nov 12, 2013 at 11:04 PM
Would you recommend upgrading to 3.0 alpha for more speed? Has it been well tested for correctness?

My current hotspot in the numerics is RankCorrelation.
Nov 13, 2013 at 1:59 AM
Edited Nov 13, 2013 at 2:00 AM
I think the tag "alpha" has a well known meaning in computing? To quote

"The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release.[2]

Alpha software can be unstable and could cause crashes or data loss. External availability of alpha software is uncommon in proprietary software. However, open source software, in particular, often have publicly available alpha versions, often distributed as the raw source code of the software. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete."
Marked as answer by zippy1981 on 11/15/2013 at 9:02 PM
Nov 14, 2013 at 10:55 PM
Thanks Don!

With RankCorrelation you're referring to Correlation.Spearman? If yes, I had a quick look at the implementation and believe we can make it significantly faster with a few changes. Even more if we're working with sorted arrays (similar to SortedArrayStatistics). We better track this in a GitHub issue though.
Marked as answer by zippy1981 on 11/15/2013 at 9:02 PM