Re: branch landing planning/scheduling meeting -> Monday 3:00p b21 pit...

[Tao Cheng]

Chris Hofmann wrote:

[EMAIL PROTECTED]">  
updates with build instructions below.

Goal is to try and get a 'strings' test build out today after trunk verifications are completed.

Would owners of the landing patches/features also provide a brief QA test plan so people can pay attention to those area in daily usage and help catching abnormalties?

-Tao

[EMAIL PROTECTED]">

Then move to libpr0n tomorrow.  An continuing on down the list.
We will check progress and do any resetting of the order
at the first few minutes of the performance meeting tomorrow at 1:30 pst

877.708.6777 meeting id 5539

Hope we can get a lot of people to help out smoke testing and
sanity checking these builds..

Chris Hofmann wrote:

 
Rough schedule for upcoming test builds before landing will be

Goals for Pre-0.8.1 tree close.

 -scc large number of string changes.  test build on Tues.?
     (scc creating a branch to build off tonight
      forwarding build instruction to chofmann for roll up)

            branch tag is STRING_081_BRANCH. don't think any further
             build instructions are needed beyond that.

 
 -pav libpr0n w/pav-cache or object. test build on wed?
     (pav forwarding build instructions to chofmann)
     (pav also sending open known bug list to chofmann)

             building my this stuff is a little tricky since I didn't
             branch the whole tree:
 

on unix:

cvs co mozilla/client.mk
cd mozilla
make -f client.mk pull_all
cvs up -l -r IMGLIB2_20010222_BRANCH
cvs up -dP gfx2
cd modules
cvs up -dP libpr0n
cd ..
cd layout/html/base/src
cvs up -r IMGLIB2_20010222_BRANCH nsImageFrame.cpp nsImageFrame.h
cd ../../../xul/base/src
cvs up -r IMGLIB2_20010222_BRANCH nsImageBoxFrame.cpp nsImageBoxFrame.h
cd ../../../../gfx
cvs up -r IMGLIB2_20010222_BRANCH `find . -name *RenderingContext*\.h
-print`
cvs up -r IMGLIB2_20010222_BRANCH `find . -name *RenderingContext*\.cpp
-print`
cd ../content/html/document/src
cvs up -r IMGLIB2_20010222_BRANCH nsImageDocument.cpp
cd ../../../..
make -f client.mk depend build_all

(and basically the same thing on windows)

Once i get in the tree, it will be a matter of just changing an ifdef to
make all this work :-)
 

 -necko cache with http://  and ftp://?  test builds on thursday?
     (gordon/darin forwarding build instructions)
       (new cache for imap will come much latter when mail performance
         branch lands)
      (should see some additional bloat in builds until
       the transition is made for full cut over to the new cache)

The new cache is already on the tip, and currently pulled.
The new files reside in
mozilla/netwer/cache/public and mozilla/netwerk/cache/src.

To build the new cache on Windows and Linux, set this environment variable:

MOZ_NEW_CACHE=1

For the mac, edit your "Mozilla [debug] build prefs" file to add this line

options     cache           1
 

Gordon
 

We can check status on getting builds and testing feedback for
these areas at the Wed. and Friday 1:30 performance meetings.

All the above could be turned on before 0.8.1 if the test builds
look ok.  we will need lots of help checking out these additional
test builds each day.  Watch for posting on the builds news groups
for identification of which builds have which new features to test.

further down the road (Post 0.9 tree open)

  first carpool after tree opens for 0.9 will be the mail performance branch.
   (mscott to send build instructions to chofmann for roll up and post)

The mailnews branch name is:
MailNews_Performance_20010208_BRANCH.

cvs co -r <branch name> mozilla/client.mak
then nmake /f client.mak pull_all, build_all
and you are in business.

The branch currently builds on all 3 platforms.

-Scott
 

bi-di should be ready to flip the ifdef  on shortly after 0.9 opens.
    (may try to get a test build out off the 0.8.1 branch if all the changes have
     landed under ifdef)

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.

Also to check on XPConnect/Dom conversion.  jst/jband,  any updates
on plans or schedules you have for landing this work?
 

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.
 
 

chris h.

Chris Hofmann wrote:

For today's meeting at 3:00p only:...

USA Toll Free Number: 888-385-9734
 PASSCODE: NETSCAPE
 LEADER: Chris Hofmann

chris h.

Chris Hofmann wrote:

> lots of stuff is on the short horizon for landing including...
> libpr0n, layout reflow improvements,  necko cache, outliner widget,
> psm 2.0, bi-di, etc., etc., .....
>
> mix to many of these landings together or mess up on the timing
> of the landings with other changes and milestones and we could
> spend lots of extra recovery time which we really can't
> afford on the current milestone schedule.
>
> We need to add some precision and improve communication
> on the landing plans much like we did a couple of years ago with
> the original necko landing.
>
> We are going to start short weekly planning meetings to:
> -get updates on the schedules for major branch landings,
> -help to streamline reviews/super reviews,
> -schedule release test builds from the various branches to run
>   extended smoke and performance tests and get builds into the
>   hands of many people to enable them to check for regressions and
>   side effects
>
> All this will help us to get a clear picture of what is working, and not
>
> working, before the branches land to move forward in the fastest way
> with the least impact on stability and the schedule.
>
> I'll also try and get a dial-in conference call number for these
> meetings
> and will publish minutes.
>
> pav, saari, gagan, gordan, darin, hyatt, putterman, lord or psm proxy,
> erik or bi-di proxy, and any others that know of big landings that
> will have wide spread effect should attend.   reviewers and super
> reviewers should also attend.
>
> In the first meeting lets rough out a timeline for when all the various
> landings might be ready in the next few weeks.
>
> Really good donuts will be served.   See you there..
>
> chris h.