In the forum, LFS progress is arguing matter and will be for a long time. My starting point is just taking a photo about that and trying to clarify the path ongoing. The aim is not whining, not moaning, not complaining, not Scirocco; although it seems such as the mixture of them. And here is coming the word : “BUT”
But because nobody knows what will be. Maybe the devs have some predictions or projections. We are in the alpha stage now and I’m really wonder how many patches needed for the beta stage and S2 out: 5 or 10 patches? Naturally more patches means more work, more time, and more turmoils in the forum.
So I figured out a some graphs those show the LFS progress stages from the beginning up to now. The method is cutting the timeline into different periods based on prefix and graphically.
PREFIX BASIS (DAYS PASSED AFTER OFFICIAL PATCHES, TODAY: 28.04.2009)
0.1B – 0.1W stage: min: 3 max: 48 avr: 16
0.1B – TODAY stage: min: 3 max: 300 avr: 74
0.2A – 0.2F stage: min: 11 max: 84 avr: 38
S1 – S1H stage: min: 22 max: 220 avr: 79
S2 ALPHA - S2 0.5Z stage: min: 8 max: 237 avr: 114
S2 ALPHA – TODAY stage: min: 8 max: 300 avr: 128
GRAPH BASIS (DAYS PASSED AFTER OFFICIAL PATCHES, TODAY: 28.04.2009)
0.1B – S1F stage: min: 3 max: 84 avr: 29
0.1B – S1H stage: min: 3 max: 220 avr: 38
0.1B - S2 ALPHA stage: min: 3 max: 220 avr: 45
0.1B - S2 0.5Z stage: min: 3 max: 237 avr: 66
0.1B – TODAY stage: min: 3 max: 300 avr: 74
S1H - S2 0.5Z stage: min: 8 max: 237 avr: 122
S1H - TODAY stage: min: 8 max: 300 avr: 135
S2 ALPHA – TODAY stage: min: 8 max: 300 avr: 128
The Prefix table shows the progress history obviously. Thus I will try to interprete the historic progress via fluctuations on the chart.
At the 0.1B - S1F period (see: Chart 1), the development progress based on day basis to the next patch is very stable. But S1H brought on a new era with 220 days record. Although there was a drastic fall to the S2 0.5L, the volatility stil increases in line with the standard deviations and max/min quotients. As of today (28.04.2009) the all time high peak has reached to 300 days. This is absolutely terrifying and seems the new record should be rise for a while.
Consequently LFS progress is getting more and more slower than before. (see: Chart 2 and 3) At this point, I think things must be changed. Otherwise we will see more longer waiting periods. Arguing doesn’t help us and almost all the suggestions have been made. I predict devs realized this. Maybe their priviliges is different from ours, but the common interest should be monitored.
I want to believe that devs could manage this dissatisfaction because, LFS proved that what they could be. Perhaps some little touchings could help us. I know coding is very complicated issue and there is no equation such as 2 + 2 = 4. But there are two main directions related to coding: Coding independent issues comparably simple ones and coding coherent features like a chain.
Imagine just a test consisted of 60 questions and 60 minuted deadline. Some questions make a group every single question is related to others. At the same time some questions are unique and independent from each other. In order to use time effectively, sometimes there is a need passing over from the questions that we couldn’t answer to new ones. If time remained, we can focus on it again. Of course the coding has a complex structure, but this logic could be implemented into the LFS.
Consequently, there are too many things to say, suggest. As mentioned before, most of them stated many times before. So no need to repeat. I just wanted to show the complete picture of LFS progress objectively.