Re: Branch Landing Updates 4-2-1

Tue, 01 May 2001 12:21:17 -0700

Title: Branch Landing Updates 4-2-1
what is a seamonkey
"Chris Hofmann" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...

Latest updates to the branch landing plan....

Next meeting Wed. at 1:30.
b21 pit or 1.877.708.6777 mtg id 7584

If you have additions to the landing plan or
updates  for any of these changes
post them or send them to me.

thanks

chris h.

http://warp/u/chofmann/voting/branches.cgi

Don't whack the tree. Avoid the Hazzards. Put it in the fairway!
Tee-Time
chofmann's Branch Landing Info Roller Upper and Carpool Reservation Hack.
A tool for planning and tracking future carpools approching the trunk
    click on project name link to add comments and branch data

    Projects on Deck LL Landing Status Information as of: Mon Apr 2 20:31:42 2001
    1. string-changes 3
  • this is for portability, robustness, and a few bug fixes.
  • scc has build on mac with no known regressions, working on windows and linux
  • 1-3-30- would like to get jrgm perf run to confirm no slowdown in use of strings in page loading
  • 3-30-1: branch tag is STRING_081_BRANCH
  • 3-30-1: ftp://ftp.mozilla.org/pub/mozilla/nightly/experimental/string/ has a mac build
  • 3-30-1: still working on win32 and Linux builds
  • 3-31-1: Commercial patch is here: http://bugscape.mcom.com/show_bug.cgi?id=4512
    		•
    2. style-sys-footprint 3
  • 3-31-1: [EMAIL PROTECTED] is working on $tyle system context sharing to reduce footprint and bloat
  • 3-31-1: http://bugzilla.mozilla.org/show_bug.cgi?id=43457 has more details
  • 3-31-1: saves a lot of memory at the expense of a moderate performance hit.
  • 3-31-1: pierre posted diffs to the bug.
  • 3-31-1: jrgm reports %4 slowdown in the test build he made.
  • 3-31-1: need to figure out what to do next..
  • 3-31-1: there are also some data on the savings in chrome and on page loading in the bug. need to get test builds in the hands of a lot of people to play with and evaluate.
    		•
    3. editor-refactoring 2
  • 3-30-1: kin and mjudge working on this. have test builds they are evaluating within the editor team
  • 3-30-1: need some putterman mail team and mail qa quick look...
    		•
    4. xul-reorg 2
  • blakeross has other smaller changes with startup/open new window speedup impact coming. should carpool and wait until we get the resent performance and mem use regressions cleared.
  • Mar30: hyatt thinks blakeross will be ready for carpool early in the week of 4/3
    		•
    5. domconversion 2
  • <3/29/01> jst now has things working in his local tree. plans to merge with jband and have a branch ready for folks to look at next week
  • 3-30-1: big honking footprint win. will involve removing lots of source files and refactoring others.
  • 3-30-1: will be extremely hard to back out after throwing the switch and landing the changes.
  • 3-30-1: schedule has moved up. may be ready for experimental builds by around 4/6.
    		•
    6. bidi 2
  • 3-30-1: erik, ftang working on this with IBM folks
  • 3-30-1: need to run comparison builds with ifdef off, and ifdef on and compare against same level of trunk builds to confirm no, or measure any, performance regressions
  • 3-30-1: gerardo should be running performance tests against experimental builds the week of 4/3
  • 3-30-1: detailed progress chart
    		•
    7. psm2.0 2
  • 3-30-1: ddrianan,lord, and javi are the contacts. branch is available
  • 3-30-1: planning on publishing a test .xpi file that will install on current trunk to give anyone an inprocess psm version.. way cool.
  • 3-30-1: experimental .xpi file should be available week of 4/3
    		•
    8. cache-level-1 2
  • 3-30-1: will provide dynamic eviction (Level 0 evicts only on shutdown) and efficient cache miss detection
  • 3-30-1: gordon: We hope to land Level 1 by early in the week of 4/3.
  • 4-2-1: Branch name = DISKCACHE1_BRANCH
    		•
    10. ldap 1
  • 3-30-1: at one point dmose was hoping to land in 0.9..
  • 3-30-1: http://bugzilla.mozilla.org/show_bug.cgi?id=17880 is the tracking bug
    		•
    11. accessibility 1
  • 3-30-1: evaughan has landed accessibilty code. api's have been tested on win32 and linux. working on getting mac up and running.
  • 3-30-1: widgets need to start figuring out how to use accessiblity code around the start of M0.9.1
    		•
    13. P3P 1
  • 3-30-1: harishd will be landing the P3P code, contributed by Tom Lendacky of IBM, into the extensions directory.
  • 3-30-1: However, the code will not be a part of the build until all intergation issue including UI work have been resolved.
  • 3-30-1: Building P3P -Win32 set MOZ_P3P=1 LINUX-Use patches Mac-Not building yet. Looking for help.
    		•
    15. cache-level-2 1
  • 3-30-1: provides a more efficient mechanism for storing the cache entry and metadata
    •

    Add a Project

    If you have a project you would like to add, please

    Completed/Retired Projects

    Project Comments
    libpr0n
  • 4-2-1: Marked Completed by chofmann: pav and saari have whacked the tree on all platforms now
    • mail-news-performance
  • 3-30-1: mscott is the main contact
  • 4-2-1: Marked Completed by chofmann: 3-30-1: branch has landed.
  • 3-30-1: All new bugs introduced with MailNews branch merge
    		•
    newcache
  • 3-30-1: all turned on. check or add to status summary=[cache] for regression buglist.
  • 4-2-1: Marked Completed by chofmann: 3-30-1: all checked in on all platforms.
  • 3-30-1: The name of the necko branch is MOZ_NEW_CACHE_20010314_BRANCH
  • 3-30-1: this is the cache formerly known as the cache-level-0
    • Need help? Send mail to     chofmann.

    Branch Landing Page

    Here's the scoop. You have big/hairy changes. Try and and land them smoothly and use this form make sure they your landing plan is communicated widely.

    Where ever, and when ever, it makes sense for the project "cache-level-1" , you should enter comments about the following Landing Tasks to let folks know what is going on and avoid train wrecks:

    1. Tell the one-line elevator story about the benefit of this change.
    2. Tell who is working on the changes and provide e-mail contact info.
    3. Provide the bug number for info more details outlining the development task.
    4. Provide summary of the scope of the change (estimated number of files, risks, etc.)
    5. Outline other development tasks that this work depends on.
    6. Outline other development tasks that depend on this checkin.
    7. Estimate the date for completing the basic development work and have it basically working somewhere..
    8. List obstacles in the way of getting basic the work done.
    9. Estimate the date for having sources checked in somewhere (patches to bug, branch, new directory, etc..)
    10. List branch name and build instructions or provide link (so other engineers can look at the code and try builds)
    11. Tell when basic work is completed and your ready for help in testing.
    12. Estimate the date for having experimental builds posted on mozilla.org
    13. Provide location of experimental build(s) when they have been posted
    14. Provide link or info about test plans or testing needs.
    15. Provide dependency bug number or bugzilla query for filing, finding and tracking any/all regressions that surface in experimental build testing evaluation.
    16. Complete a review/assessment of regression bug list (uber landing planner(s))
    17. Estimate the date for carpool
    18. Schedule the carpool.
    19. Provide status updates as the car pool landing progresses
    20. Recap the landing and move to the completed landing list.
    21. Drink Tequila.
    Comment on one of the areas listed above>
    Bump the Landing Level (LL) for this project when bolded items are completed.
      project name and step completed:
    Change status of this project to Complete.
      Explanation:
      your name :

      Reply via email to