Migration of profiles prior to SM 2.0 removed with 2.8

[rsx11m]

So, Mozilla Core wants to get rid of some functionality which was necessary to import/migrate profiles prior to Firefox 0.9.x stored in the Mozilla Suite style (bug 679352). There is a corresponding Thunderbird version (bug 689120) to remove that functionality from comm-central as well. My guess is that it somehow (i.e., equally) would affect SeaMonkey as well.

Consequences? Starting with, let's say, SM 2.6, profiles from SeaMonkey 1.x, Netscape 6.x/7.x, and early (pre-toolkit) Firefox/Thunderbird version would no longer be recognized and migrated to the new format used since 2.0 (which was introduced much earlier by Firefox/Thunderbird).

Workaround: Users on 1.x or earlier would have to migrate to 2.[0-5] first, then update to 2.6 or later to be current.

I'm wondering how many users are actually still on SM 1.x or Netscape/Suite versions, thus would be affected by dropping that migration code...

[rsx11m]

Ok, this is bug 689437 for SeaMonkey now. Anybody having concerns about this step should comment in either of these bugs.

[rsx11m]

The changes on the core side have been checked in last night (bug 679352), so this will become effective with SeaMonkey 2.8 for sure.

Trunk builds are currently busted due to this change, thus no 2.8a1 nightlies at this time.

[Arlene Bingham]

I am a newbie but would like to ask a question about this bug 679352. How does it effect mozilla's functionality?

[rsx11m]

This should only be relevant if you are migrating from an older version (i.e., SeaMonkey 1.x, the old Mozilla Suite, or Netscape 6.x/7.x) to a current SeaMonkey release. In this case, you'd have to install, e.g., SeaMonkey 2.0.14 first to migrate that profile to the new format, then install a current release over it which should perform any remaining migration steps.

This has only an effect for migration tasks and shouldn't have any impact on day-to-day work.