Merging tree-ssa into mainline

[Mark Mitchell <mark at codesourcery dot com>]

The GCC SC has decided to allow a merge from the tree-ssa branch into 
the mainline, following the guidelines set out below:

(1) The tree-ssa team will prepare a document outlining criteria for
  merging tree-ssa into the mainline.

  It will, for example, cover checking that coding conventions and
  documentation are in order, cover, indicate the testing that will
  be performed, and highlight current open PRs that will be fixed.
  It might also discuss SPEC benchmark performance and/or
  compile-time performance.

  This document will be distributed to the SC and the broader
  community, and, after revision, approved by the SC.

  [Although not discussed on the call, I propose giving the tree-ssa
  team 1-2 weeks to prepare this document, circulate it to the
  community, gather responses, and submit what they feel is a
  finished draft to the SC for approval.]

(2) The tree-ssa team will then concentrate on meeting those
  requirements, within approximately a two-month window.

  If the requirements are met, as expected, the branch will be
  merged into the mainline.  Until the merge occurs, the mainline
  will remain in Stage 1 -- but major changes likely to be
  disruptive to the tree-ssa merge will need to be cleared by the
  tree-ssa team.  During this time, the tree-ssa branch will be
  mostly closed to new contributions and the various players will
  concentrate on making the fixes and improvements necessary to get
  the merge done.

  If the requirements are not met, the SC will have to decide
  whether to extend the deadline or to proceed without tree-ssa for
  GCC 3.5.

(3) Following the merge, the tree-ssa team will commit to helping
  people fix problems caused by the merge, including problems on
  embedded systems, etc.

  The mental model here is that there will be an informal contract
  between the tree-ssa team and the SC, whereby the SC will give
  tree-ssa a chance to merge and help keep things quiet on the
  mainline to facilitate that, and, in turn, the tree-ssa team will
  try to merge as expediently as possible and will commit to solving
  problems after the merge.

The SC will now look forward to a submission from the tree-ssa team.

--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com