8 Jun
2011
8 Jun
'11
3:08 p.m.
On 6/7/11, James Cook
The name of the field could be better, though. On first exposure, people tend to think "stability: experimental" or "stability: unstable" means the package is likely to crash (For those who don't know, it means the API is likely to change in future releases).
What is the way to indicate actual code stability? Some packages on Hackage definitely have "broken parts." Tom