Bon Echo Beta1 planning/status meeting tomorrow at 11:30am PDT
Mike Schroepfer
Tonight is the code freeze - I'd like to do a quick meet tomorrow at
11:30AM PDT to plan out a couple of the last steps before b1. The full
b1 bug list is here
(https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=nowords&keywords=fixed1.8.1+verified1.8.1&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-firefox2%2B&field0-1-0=target_milestone&type0-1-0=equals&value0-1-0=Firefox+2+beta1&field0-1-1=target_milestone&type0-1-1=equals&value0-1-1=mozilla1.8.1beta1)
Agenda:
1) Review known risk areas (below)
2) Review any new risk areas
2) Review plan for beta 1 release:
a) QA plan
b) Build/release
c) Release notes/website changes
Dialin: 1-866-216-2181
IRC: #bonecho
Best,
Mike
There are areas of concern to me:
https://bugzilla.mozilla.org/show_bug.cgi?id=340677
Since it's a large patch. We could use help testing the trunk builds to
make sure the pref panel is still functioning properly
https://bugzilla.mozilla.org/show_bug.cgi?id=341190
Because it involves both client and server AUS. I'd prefer to no defer
this one since b1->b2 upgrades is a great place to catch issues.
https://bugzilla.mozilla.org/show_bug.cgi?id=336373
JS 1.7 - which has mostly been on trunk and has good automated coverage.
This makes b1 or misses the release.