Could get real interesting around the end of next week again
with lots of stuff on the horizon for landing.
I'm working on a new tool to help gather and communicate
up-to-date info on major things hitting the tree.
Hoping to get the tool posted on mozilla.org next week
so folks can update with live information.
If your inside the netscape firewall you can help by
adding details about the areas listed below into the form..
If your outside the firewall and you want to provide updates
send them to me until we get this posted on mozilla...
Next Branch Landing Review Meeting is planned for
Wed. April 4. 1:30p
b21 Pit or 1.877.708.6777 mtg code 5539
thanks.
chris h.
1.Tell the one line elevator story about the benefit of
this change.
2.Provide the bug number for info more details outlining
the development task.
3.Provide summary of the scope of the change (estimated
number of files, risk, dependency on this code.)
4.Estimated date for completing the basic development
work and have it basically working somewhere..
5.List obstacles in the way of getting basic the work
done.
6.Estimate date for having sources checked in somewhere
(patches to bug, branch, new directory, etc..)
7.List branch name and build instructions or provide link
(so other engineers can look at the code and try builds)
8.Tell when basic work is completed and your ready for
help in testing.
9.Estimate date for having experimental builds posted
on mozilla.org
10.Provide location of your latest experimental
build(s) to get help in testing before the landing
11.Provide link or info about test plans or testing needs.
12.Provide dependency bug number or bugzilla query for filing,
finding and tracking any/all regressions that
surface in experimental build testing evaluation.
13.Complete Review/assessment of regression bug list (uber landing
planner(s))
14.Estimate date for carpool
15.Schedule the carpool.
16.Provide status of car pool landing
17.Recap the landing. and move to the completed landing list.
http://warp/u/chofmann/voting/branches.cgi
Title: Branch Landing Updates 3-30-1
Tee-Timechofmann'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 | Landing Level |
Landing Status Information:
|
|---|
| 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 linux1-3-30- would like to get jrgm perf run to confirm no slowdown in use of strings in page loading3-30-1: branch tag is STRING_081_BRANCH3-30-1: ftp://ftp.mozilla.org/pub/mozilla/nightly/experimental/string/ has a mac build3-30-1: still working on win32 and Linux builds |
| 2. 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 |
| 3. xul-reorg | 2 | [EMAIL PROTECTED] and blakeross have other smaller changes with 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 |
| 4. 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 week3-30-1: big honking footprint win. will involve removing lots of source files and refactoring other.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. |
| 5. bidi | 2 | 3-30-1: erik, ftang working on this with IBM folks3-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 regressions3-30-1: gerardo should be running performance tests against experimental builds the week of 4/3 |
| 6. editor-refactoring | 2 | 3-30-1: kin and mjudge working on this. have test builds they are evaluating within the editor team3-30-1: need some putterman mail team and mail qa quick look... |
| 8. 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 |
| 10. 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. |
Add a Project
If you have a project you would like to add, please
Completed/Retired Projects
| Project | Landing Level | Comments
|
|---|
| libpr0n | XXX | 3-30-1: Marked Completed by chofmann: pav and saari have whacked the tree on all platforms now
|
| mail-news-performance | XXX | 3-30-1: mscott is the main contact3-30-1: Marked Completed by chofmann: 3-30-1: branch has landed.
|
| newcache | XXX | 3-30-1: all turned on. check or add to status summary=[cache] for regression buglist.3-30-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 |
Need help? Send mail to chofmann.