Linked by Thom Holwerda on Fri 3rd Sep 2010 22:34 UTC, submitted by Mike C
Thread beginning with comment 439500
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2006-01-26
Which is exactly what you would expect from alpha releases.
"Alpha" generally indicates that a piece of software is "incomplete" - meaning that there are still pieces being developed. These developments are always likely to create regressions and stability problems.
When software reaches the "Beta" stage, that is generally when software reaches a "feature freeze", and only bug fixes are being worked on.
It is not uncommon for 2nd or 3rd alpha releases to have more bugs than before - usually because you are nearing a "feature complete" state and developers tend to be rushing to add the missing bits so that bug fixing and polishing can begin ASAP. I can only hope that's what is happening here