SeaMonkey/StatusMeetings/2011-11-01: Difference between revisions

Line 64: Line 64:


==== 2.Next ====
==== 2.Next ====
* We need to make sure that anything that landed on comm-beta (for TB) or mozilla-beta (for FF) which affected non-shared code and which fixed regressions will be fixed on our side, too. Please mark bugs we feel *need* to land on a particular train tracking+ or tracking? so that when I go to do a release I can be sure I don't miss anything.
* Please make sure that anything that landed on comm-beta (for TB) or mozilla-beta (for FF) which affected non-shared code and which fixed regressions will be fixed on our side, too. Please mark bugs we feel *need* to land on a particular train tracking+ or tracking? so that when we to do a release we can be sure that we don't miss anything.
** We also need to try harder to fix regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.
** Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.
** We have to be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.
** Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.
* Please help updating the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go.
* Please help updating the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go.


Confirmed users
2,595

edits