Subproject #3: 700k-800k sequences to 100 digits

[henryzz]

Here is the next subproject for 700k-800k. I expect that 600k-700k will be next possibly depending on the mystery work that affected the end of the last suproject.

This subproject is complete! Subproject #5 has started.

Milestones:

700k-705k 06/10/09 - 20/10/09 (14 days)
705k-710k 15/10/09 - 30/10/09 (15 days)
710k-715k 19/10/09 - 04/11/09 (16 days)
715k-720k 24/10/09 - 13/11/09 (20 days)
720k-725k 05/11/09 - 22/11/09 (17 days)
725k-730k 14/11/09 - 11/12/09 (27 days)
730k-735k 27/11/09 - 17/12/09 (20 days)
735k-740k 06/12/09 - 31/12/09 (25 days)
740k-745k 17/12/09 - 02/01/10 (16 days)
745k-750k 27/12/09 - 08/01/10 (11 days)
750k-755k 30/12/09 - 10/01/10 (11 days)
755k-760k 31/12/09 - 04/01/10 (4 days)
760k-765k 02/01/10 - 20/01/10 (18 days)
765k-770k 10/01/10 - 19/01/10 (9 days)
770k-775k 01/01/10 - 12/01/10 (11 days)
775k-780k 25/12/09 - 09/01/10 (15 days)
780k-785k 13/01/10 - 22/01/10 (9 days)
785k-790k 15/01/10 - 22/01/10 (7 days)
790k-795k 17/01/10 - 04/02/10 (18 days)
795k-800k 27/01/10 - 01/02/10 (5 days)

Subproject completion date: 4 February 2010
Total subproject length: 121 days
Average time per 5k chunk: 14.4 days

[BigBrother]

Reserving 700056

[Greebley]

Reserving the 704's:
704016, 704106, 704376, 704700, 704712, 704850, 704900, 704940

[Mini-Geek]

Milestones:
700k-705k first reservation: 6/10/09
700k-705k complete: 15/10/09 (5k in 9 days)
705k-710k first reservation: 13/10/09

(this example assumes we finish to 700-705 on Oct 15 and first got a reservation on 705-710 on Oct 13)

Unless anybody, particularly the other mods, have a problem with this vs the old way, I think this is how we should track the milestones from now on. Makes much more sense whenever sequences are completed out-of-order (just take a look at the number of "in 0 days" listings on the last subproject!) or some 5k range was done before we got to it or something.
Note that these are sorted by seq number, not by date.

[BigBrother]

700056 is done.

Reserving 700128

[Batalov]

Taking 701460, 701976, 702828

[henryzz]

Originally Posted by Mini-Geek

(this example assumes we finish to 700-705 on Oct 15 and first got a reservation on 705-710 on Oct 13)

Unless anybody, particularly the other mods, have a problem with this vs the old way, I think this is how we should track the milestones from now on. Makes much more sense whenever sequences are completed out-of-order (just take a look at the number of "in 0 days" listings on the last subproject!) or some 5k range was done before we got to it or something.
Note that these are sorted by seq number, not by date.

looks brilliant

[axn]

Originally Posted by Mini-Geek

(this example assumes we finish to 700-705 on Oct 15 and first got a reservation on 705-710 on Oct 13)

Unless anybody, particularly the other mods, have a problem with this vs the old way, I think this is how we should track the milestones from now on. Makes much more sense whenever sequences are completed out-of-order (just take a look at the number of "in 0 days" listings on the last subproject!) or some 5k range was done before we got to it or something.
Note that these are sorted by seq number, not by date.

Since lines are at a premium, why not: [range] [start date] [end date] [elapsed days] ?

[Mini-Geek]

Originally Posted by axn

Since lines are at a premium, why not: [range] [start date] [end date] [elapsed days] ?

Milestones:

700k-705k 06/10/09 - 15/10/09 (09 days)
705k-710k 13/10/09 - 23/10/09 (10 days)
710k-715k 22/10/09 - ???

I also added a dash to make it a bit clearer, (though about adding a legend, but it doesn't align with the rest) and added a leading 0 to one-digit values so that it'll all line up. (should be easier to read when there's a lot, more like a table)
I think that looks good...or we could do it a more terse, [code]less way, like you suggested:

Milestones:
700k-705k 6/10/09 15/10/09 (9 days)
705k-710k 13/10/09 23/10/09 (10 days)
710k-715k 22/10/09 ???

Personally, I like mine in the code tags best so far.

[Greebley]

I like the dash between times and aligned.

Done with 704016, 100 digits, 2^2*3*7

[axn]

Originally Posted by Mini-Geek

I also added a dash to make it a bit clearer, (though about adding a legend, but it doesn't align with the rest) and added a leading 0 to one-digit values so that it'll all line up. (should be easier to read when there's a lot, more like a table)
I think that looks good...or we could do it a more terse, [code]less way, like you suggested:
Personally, I like mine in the code tags best so far.

All good! The use of [ code ] tag was always implicit in my suggestion