Re: draft lithium release plan
Ed Warnicke (eaw) <eaw@...>
Actually, karaf in Helium is the *perfect* example of why KDC is crucial.
We *rushed* the Helium Simultaneous Release Plan out the door. We did *not* KDC karaf for Helium. We *did* make a series of commitments to figure stuff out at various other milestones. We did not *actually* figure those things out at those milestones. KDC is about *preventing* that kind of a problem in the future. Its why its crucial.
Again, the karaf issue was a *failure* to KDC when we should have because of a *rush* to get out a SR Plan. I’d like us to *not* repeat that particular mistake again.
(note: much love to karaf, apologies to karaf that its being used for this example :( ).
OK… I think that’s part of the Milestone Reporting by the projects. I know when I did Milestone Reporting at least for controller that was done.
I think the most that the TSC or Release staff can do is confirm that the *projects* reported on their content deliveries at Milestones… which I think is actually goodness :)
Totally, as long as M1 comes no less than 4 weeks after that :)
A huge amount of suffering has come in the past of *not* having good ones at M1… I think we really need to *strive* for good ones at M1. The ‘lets just throw something over the wall for the release plan’ has been a problem in the past,
and I prefer we not encourage it by being cavalier here.
Fair point, can we talk to our amazing sysadmins
a) Being ready to deal with the expected projects
b) What a reasonable SLA for provisioning would be there?
:) :) :) :)
I strongly believe we can KDC something reasonable here :)
I think I see where you are going here… M3 being functionality freeze, I think that is probably the appropriate place for it. I’d suggest we work out a column in the Release Plan template for projects though to mark it :)
Could you help me understand the reasoning in giving a 24 hours spread instead of a datetime certain?