Ray_Net wrote:
In my opinion, the migration issues are MAJOR ISSUES ...
They are, but 1) they are really hard to get a grip on, as most people don't repeatedly test them, and being well-reproducible and well-reproduced is one of the major things to get well-reported specific problems fixed (I'll leave out for the moment that many of those problems are not well-reported bugs and not specificly enough described to even be able to try and reproduce them). 2) Once data is being migrated or otherwise moved to a new 2.0 profile, people are over those problems and never see them again - so while they are _very_ painful for the moment when they happen, the pain is completely gone once the data gets over to 2.0 in some way.
Of course, we all would be happy if we didn't see those problems in the first place, but the only scenario I can see that we go mostly pain-free there is if someone comes up and spends a whole lot of time on the migration code, and we at the same time have some very specific reports of where we go wrong with exact circumstances that lead to the failures. And, as unfortunate as that is, I really doubt that someone will come up that easily - unless you are that someone and are lurking around here waiting to become the next SeaMonkey superstar. If you are, I'm all for casting you in that role as migration superman!
We're trying to find solutions for some of the migration problems where we find out what exactly the problems are and where we know good ways to solve them. Still, please don't expect miracles from us. We're producing the best software we can with our relatively small team, but we know it might not be good enough for everybody - still we hope it is for most of you.
Robert Kaiser _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
