Closed Bug 1566772 Opened 6 years ago Closed 6 years ago

Remove Netscape migration

Categories

(Thunderbird :: Migration, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jorgk-bmo, Unassigned)

References

Details

See Also: → 224699

Yeah I think so

Flags: needinfo?(mkmelin+mozilla)

Looks like I cheered too early. Netscape import is used for SeaMonkey import, see:
https://searchfox.org/comm-central/rev/904df8b94946eeca84b45a74990f6bddbeae2862/mail/components/migration/src/nsSeamonkeyProfileMigrator.h#16
class nsSeamonkeyProfileMigrator : public nsNetscapeProfileMigratorBase

I've seen SeaMonkey import show up in the import dialogue
https://searchfox.org/comm-central/rev/904df8b94946eeca84b45a74990f6bddbeae2862/mail/locales/en-US/chrome/messenger/migration/migration.dtd#14
and there doesn't appear to be a Netscape import as such.

It would only be interesting to know whether SM import works or whether bug 224699 shows up for SM import as well. FRG, does SM import work?

On the other hand, I found left-overs from the OE Import removal:
https://searchfox.org/comm-central/search?q=oeImportMsgs.properties&case=false&regexp=false&path=

I'll close this as invalid since we will need SM import in the future and I'll file a new bug for the OE stuff.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(frgrahl)
Resolution: --- → INVALID

I'll close this as invalid since we will need SM import in the future and I'll file a new bug for the OE stuff.

SM comm-central is broken and something for long winter nights. We keep it building right now but personally I don't care about anything Gecko after 60.

That said I think it should be removed. It is 2019 not 1995 and even importing from early SeaMonkey versions is no longer supported. I was unable to test changes here in the past.

Flags: needinfo?(frgrahl)

Is there a misunderstanding? I'd like to give people the opportunity to migrate from SM "60" 2.57 (right) to TB. And for that, it would be good to have the SM import.

Ok thought there is/was some shared code involved which should go.

You need to log in before you can comment on or make changes to this bug.