Bugzilla:Meetings:2006-11-28: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
Line 2: Line 2:


* The log of the meeting is available [http://bugzilla.glob.com.au/irc/?c=bugzilla-meeting&a=date&s=28+Nov+2006&e=28+Nov+2006 here].
* The log of the meeting is available [http://bugzilla.glob.com.au/irc/?c=bugzilla-meeting&a=date&s=28+Nov+2006&e=28+Nov+2006 here].
* We will push [https://bugzilla.mozilla.org/show_bug.cgi?id=319598 bug 319598] (add saved-reports support) to 3.2 as it's not ready on time. This was the last enhancement bug targetted to 3.0. This leaves us with 12 "real" blockers for 3.0 RC1.
* There are two specific blockers we want to see fixed before releasing 2.23.4: [https://bugzilla.mozilla.org/show_bug.cgi?id=360710 bug 360710] and [https://bugzilla.mozilla.org/show_bug.cgi?id=361252 bug 361252].
* We hope the new MySQL 4.1.22 doesn't introduce backwards-incompatibilities, as we had with MySQL 5.0.25+.
* Some b.m.o-specific news: justdave will upgrade b.m.o to 2.23.3+ in a few weeks.
* The mailing lists that are on bugzilla.org will be doing the majordomo2 -> mailman transition.
* The next meeting will take place on Tuesday, December 12, same time.

Revision as of 14:41, 6 January 2007

22nd IRC meeting: Tuesday, November 28th, 2006 at 19:00 GMT

  • The log of the meeting is available here.
  • We will push bug 319598 (add saved-reports support) to 3.2 as it's not ready on time. This was the last enhancement bug targetted to 3.0. This leaves us with 12 "real" blockers for 3.0 RC1.
  • There are two specific blockers we want to see fixed before releasing 2.23.4: bug 360710 and bug 361252.
  • We hope the new MySQL 4.1.22 doesn't introduce backwards-incompatibilities, as we had with MySQL 5.0.25+.
  • Some b.m.o-specific news: justdave will upgrade b.m.o to 2.23.3+ in a few weeks.
  • The mailing lists that are on bugzilla.org will be doing the majordomo2 -> mailman transition.
  • The next meeting will take place on Tuesday, December 12, same time.