I don't have a graph program am too lazy myself, but why don't you calculate a projected slop based on the behavior from past countdowns?
I'm pretty sure this is the first update where Toady's kept a countdown like this. In about a month I'll update it again and we'll see where we stand (unless DF comes out before the 19th of January lol)
He started the format for the number then newspost on
06/13/2008Before then he would make a passing comment on the number of bugs//lines left to go. (Ultimately before it reached 0 for DFv39a)
Boring news analysing crap in spoiler. Half assed job of it too.
First mention is see is on 02/22/2008 for 332 bugs, but it goes up and he set a cap for 350 before working on the next thing, which on 03/12/2008 he was 15 above(365)
then on 06/13/2008 he started with the format, at 261. Assuming that combination of bugs being added with the stages 4-9, you could guess the total number >.>
and a month later on 07/14/2008 he gets to 0
Although looking back on it, he doesn't provide enough data until really the end running stretch between last version of DFv38 and DFv39, which for almost exactly a month had him go down basically 250. Not that we should base anything on that... But hell, analysts do it all the time!
Horrible way to guess outcomes too. But it comes out to around 4 months more, or April... That is if he does the same progress as before and doesn't come across sub-lists that take forever, or make new bugs.
Author
Topic: Graph of items remaining vs time (Read 2373 times)