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)
-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)
-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)
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)
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?
chris h.
Chris Hofmann wrote:
For today's meeting at 3:00p only:...USA Toll Free Number: 888-385-9734
PASSCODE: NETSCAPE
LEADER: Chris Hofmannchris 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.
