[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:220.127.116.11) Gecko/20100325 Shredder/3.0.5pre] (nightly) I tried "thunderbird -P testprofile -migration". "Netscape 4.x" lists my NS 4.x profile :-) "Netscape 6, 7, Mozilla 1.x and SeaMonkey" lists my SM 2.x profiles only. There's no way I can select my SM 1.x profiles :-( I don't think SM 2.x profiles should hide SM 1.x ones. (I don't think this is bug 384615, is it?) *** Additionally, I would suggest to split this into two options: *"Netscape 6, 7, Mozilla 1.x and SeaMonkey 1.x" *"SeaMonkey 2.x" (and whatever other apps which use the same kind of profiles) Though l10n freeze probably makes that possible on TB 3.1+ only :-/
Ftr, I would want to be able to do this to compare/QA the migration result/issues between SM 2.0+ and TB 3.0+. Yet, mixed SM 1.x and 2.x profiles could be a real-life case: I mean if someone actually intended to migrate from SeaMonkey to Thunderbird ;->
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:18.104.22.168pre) Gecko/20100328 Lanikai/3.1b2pre] (nightly) [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a4pre) Gecko/20100328 Shredder/3.2a1pre] (nightly) Same on trunk(s).
blocking-thunderbird3.0: ? → ---
status-thunderbird3.0: --- → ?
Version: 3.0 → Trunk
Summary: TB 3.0 migration from SM 1.x: lists SM 2.x profiles only → TB 3.x migration from SM 1.x: lists SM 2.x profiles only
We wouldn't hold Tb 3.1 for this.
blocking-thunderbird3.1: ? → -
I don't think this issue is enough to have wanted status. Whilst some users may have older profiles, I think the typical case is that users will want to migrate across their latest profile to Thunderbird, and its probably going to be just a few advanced users that want to do the weird cases. This doesn't fit into wontfix, and I don't think it is wanted - I just wouldn't flag it as a semi-priority above all the other bugs that we have.
status-thunderbird3.0: ? → ---
status-thunderbird3.1: ? → ---
You need to log in before you can comment on or make changes to this bug.