lets review the status of recent landings and figure out
which landing are ready to come next and what is
need for smooth landings in each area..

just over 3 weeks to 0.9....

join brendan and I for "branch talk" each friday at 1:30p pst
b21 pit or 877.708.6777 mtg id 3531

I'll roll the results of the meeting up and post over the weekend.

Here are the folks that need to be there or call in  or send proxies
to recap or talk about the status of their landing, current bug lists,
or plans for upcoming landings.   If there are others in the works
or you having problems with getting reviews or supper reviews
this is a good meeting to get to...   supper reviewers/reviewers
remember to channel folks to this meeting if the changes look
large or a bit on the scary side..

recap and current bug list status...
 -mscott mail perf
 -gagan,gordon,darin, beard on necko cache
 -pav,saari on libpr0n
 -hewitt,blakeross,... - xul reorging

future landings updates
 -scc large number of string changes.
 -bidi  - erik
 -lord  javi ddrianan
     First test builds of basic PSM 2.0 features (https://, etc..) look
like they
     should be available round the end  of March.  About 6 weeks of
development
     work after that to finish up PSM features.
 -jband/jst XPConnect/Dom conversion.
     The XPConnect/DOM conversion landing will definitely be post
     mozilla0.8.1, and given where we're currently at I'm not sure we'll
get
     to a point where we'll want to land this very early in the
mozilla0.9
     cycle either. Given the nature of the DOM change I don't feel good
about
     landing this *just* before a milestone, so these changes could land

     either just after the tree opens for mozilla0.9 (unlikely), or
     immediately when the tree opens for mozilla0.9.1, or right in
between,
    depending on how things work out. I'll have to wait for XPConnect
    flattening from jband (coming rsn) before I can say more about the
    schedule for landing these changes. Jband is likely to wanto land
the
    XPConnect changes separately before the DOM changes go in.


Reply via email to