Engineering Schedule
Robert Spanton
Now that the kickstart date for SR 2010 has been set, we can generate a
schedule for how we're going to ship the hardware on time [1].
The kickstart date that I believe has been set (see the meeting minutes
to make sure I'm correct...) is the 26th of September. This is my
schedule proposal working backwards from that date:
** 26th Sept: Ship hardware and software
Further software features may now be shipped.
All affected software must go through our
testing procedures before shipping (see future
discussion of how our testing procedures are
going to work...).
** 26th Aug: Software feature freeze. (Including firmwares)
1 month of testing begins.
All software will be branched from trunk at this
point, to create a "2010" branch. I propose
that we shoot anyone committing new features to
the 2010 branches.
** 26th July: Hardware assembly begins
** 12th July: Hardware freeze.
2 weeks of part procurement (NB: Part lead-times must be
analysed now, and those with longer lead times must be
ordered earlier.)
** Now: Development and testing iterations begin (continue)
** Yesterday: Funding is acquired for manufacture.
This schedule gives us 10 weeks from now to sort out any hardware
changes. As I have already announced, Tom and I have begun the
beagleboard upgrade with a target of having it sorted within this time
(having a prototype that's functional, unmodified, and identical to the
one that we'll ship).
Once this schedule has completed, we can work out the (much longer)
development schedule for SR 2011.
Comments are welcome.
Rob
[1] "on time" means all teams leaving kickstart with fully tested and
functioning kit.
p.s. I sent this to srobo rather than srobo-elec because it affects more
than just the electronics. Also, Jeremy told me to; blame him.