Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dsdp-tm-dev] I-Build schedule


I agree with the schedule you've outlined. I think we should have test
candidates at least a week before our testing is to begin, in case we have
problems with the builds and we need a day or two to resolve them, like we
did with this milestone. Targeting I20070329 as the first M6 candidate
sounds good.

Having to be at API freeze and the plan items completed by M6 is in line
with our initial project plan, and I think that's fine.


Kushal Munir
Websphere Development Studio Client for iSeries
IBM Toronto Lab, 8200 Warden Ave., Markham, ON
Phone: (905) 413-3118        Tie-Line: 969-3118
Email: kmunir@xxxxxxxxxx

             David Dykstal                                                 
   >                                                  To 
             Sent by:                  dsdp-tm-dev@xxxxxxxxxxx             
             dsdp-tm-dev-bounc                                          cc 
                                       [dsdp-tm-dev] I-Build schedule      
             02/27/2007 01:35                                              
             Please respond to                                             
             Target Management                                             

Now that we've put M5 out I believe it is time to have a firm I-Build
schedule. IBM's internal builds that absorb RSE are done on Thursdays with
respins on Fridays so I'd like to propose that we do I-Builds sometime
around 0900 UTC on Thursdays with a respin at 0900 UTC on Friday if
necessary. These builds should be sanity tested. Changes should be
stabilized prior to the build, only complete changes accepted, and an
i-build version boundary established in CVS.

I'd also like to propose that our M6 final candidate (due on Friday April
6) be available on the same schedule - that is the final respin build would
be available no later than 0900 UTC on Friday April 6. This implies that we
do some substantial testing on candidates prior to that. I propose we adopt
our I20070329 build as our first M6 candidate and produce candidates each
morning at 0900 UTC until April 5. April 5 should be our last build with
the respin on Friday being for emergencies only.

Our M7 schedule should be similar, but note that we are freezing API,
externalized strings, and user documentation with M6 so that we can
translate in time for release.

This puts a burden on all of us to have all the API and plan items finished
by March 29. M7 becomes a "fixes-only" milestone.

David Dykstal

dsdp-tm-dev mailing list

Back to the top