SeaMonkey/StatusMeetings/2008-10-21: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 85: Line 85:
=== Any other business? ===
=== Any other business? ===
* Someone will need to look into porting kill-rdf stuff to SeaMonkey, as the kill-rdf repository is now at the point where the main folder setup is now entirely divorced from RDF. I ([[User:jcranmer|jcranmer]]) would nominate such a bug to be blocking SM 2.0, but I am not a SM developer.
* Someone will need to look into porting kill-rdf stuff to SeaMonkey, as the kill-rdf repository is now at the point where the main folder setup is now entirely divorced from RDF. I ([[User:jcranmer|jcranmer]]) would nominate such a bug to be blocking SM 2.0, but I am not a SM developer.
** If this repo landing breaks seamonkey, then it is *definately* blocking, and I'd suggest blocking the landing.
** If this repo landing breaks seamonkey, then it is *definately* blocking, and I'd suggest blocking the landing. (--[[User:Callek|Justin Wood (Callek)]])
** If not, I'd say "wanted SM2" but not "blocking" ;-)
** If not, I'd say "wanted SM2" but not "blocking" ;-) (--[[User:Callek|Justin Wood (Callek)]])

Revision as of 21:17, 20 October 2008

« last meeting | index

SeaMonkey Meeting Details

Agenda

Action Items

  • any?

SeaMonkey 2 Alpha 2

Bug Queries

open blockers all blockers blocker requests

  • Freeze target is 18th November 2008.

Longer-Term SeaMonkey 2 Planning

open wanted wanted requests

Major wanted/needed features:

  • bug 381157 Download manager.
    • Updated patch[es] on Bug to Hg repo
    • Have some local changes to account for architectural changes
    • Examining both xpfe/ and toolkit/ based code for other locations that may need fixing to ease final review.
    • No progress dialoges yet, nor xpfe-like DLMGR window.
  • bug 390025 Kill-wallet (password manager).
    • Standard8 has started on some test cases for existing code (to provide reassurance that we end up migrating properly).
  • bug 382187 Places history.
    • status/progress?
  • bug 36810 Session restore.
    • waiting for review, patch for turning to error page also ready.
  • bug 394288 / bug 413385 Toolbar customization.
    • The toolbarbutton size/mode sub-bug has a few more nits to address.
    • No progress at the moment. I'll resume working on this at the end of October. Ratty.
  • bug 456757 Modern theme update.
    • No progress reports available.

Roundtable

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status)

ajschult

biesi

Callek

  • Probably unable to attend this meeting again :(
  • Worked on DLMGR more
  • Actively reviewing patches to comm-central's client.py (and watching other build* bugs in that area)

IanN

KaiRo

  • As always, my blog has more detailed status about my work

mcsmurf

  • Continued working on bug 453797 (Port Bug 392303 (Simplify installer changes) to SeaMonkey installer), patch is almost ready for review, need to fix some small things
  • The patch will probably be one big patch, will try to separate the patch into smaller patches

Misak

  • bug 36810 (session restore)
  • bug 459550 (Port Bug 448976 (turn the Session Restore prompt into an error page) to SeaMonkey)
  • bug 425480 (non-ASCII characters should be decoded in the urlbar)
  • bug 455877 (port Bug 254714 to SeaMonkey)
  • Bug reporting and bug triage.

Mnyromyr

MReimer

Neil

Ratty

sgautherie

Standard8

  • Gave gristmill a try on Thunderbird. Potentially good QA tool, give feedback to them and start using it.
  • Thunderbird release driving work now almost zero, back to fixing bugs!

stefanh

wladow

Any other business?

  • Someone will need to look into porting kill-rdf stuff to SeaMonkey, as the kill-rdf repository is now at the point where the main folder setup is now entirely divorced from RDF. I (jcranmer) would nominate such a bug to be blocking SM 2.0, but I am not a SM developer.
    • If this repo landing breaks seamonkey, then it is *definately* blocking, and I'd suggest blocking the landing. (--Justin Wood (Callek))
    • If not, I'd say "wanted SM2" but not "blocking" ;-) (--Justin Wood (Callek))