Possible bug between process import and the use of node_object_prepare

Hi all,

I am not sure if it is a bug of migrate or not, I think yes, and I also think that it is a problem with the use of property is_new.
Migrate set this value correctly, but, as you can see, node_object_prepare set status or other properties not depends on the value of is_new, but if this value is present.

In second migrations, when you try to update a node, node_object_prepare set status values as true or "1", as you prefer, even when you removeFieldMapping for this scenario. I think "is_new" should be set only when node is new, and It shouldn´t be set if it is an old node.

function node_object_prepare($node) {
  // Set up default values, if required.
  $node_options = variable_get('node_options_' . $node->type, array('status', 'promote'));
  // If this is a new node, fill in the default values.
  if (!isset($node->nid) || isset($node->is_new)) {
    foreach (array('status', 'promote', 'sticky') as $key) {
      // Multistep node forms might have filled in something already.
      if (!isset($node->$key)) {
        $node->$key = (int) in_array($key, $node_options);
      }
    }
    global $user;
    $node->uid = $user->uid;
    $node->created = REQUEST_TIME;
  }
  else {
    $node->date = format_date($node->created, 'custom', 'Y-m-d H:i:s O');
    // Remove the log message from the original node object.
    $node->log = NULL;
  }
  // Always use the default revision setting.
  $node->revision = in_array('revision', $node_options);

  node_invoke($node, 'prepare');
  module_invoke_all('node_prepare', $node);
}

As you can see, this not respect the old property of status, and It is a nightmare.

I could set the correct value recovering the old value by node_load, by I think It is not a correct approach.