Linaro GCC 4.6 Hosting

There's been a discussion about tracking what-will-become GCC 4.6 while it is in stage three, how to do it, and where to do it.

Assumptions:

  • All merge work is done by Linaro, so our choice of tools doesn't matter to upstream
  • We won't merge the branch as a whole. Patches will still land one-by-one
  • We treat our work as a 'feature branch', where the feature is improve ARM performance

Feature

Upstream SVN

Launchpad Bazaar

Technical related

Can get write permission

Y1

Y

Fast enough for development

Y2

Y3

Fast enough for release

Y4

Y

Easy to merge from trunk

1/25

Y6

Easy to merge to trunk

1/2

Y

Same workflow in stage 1 and stage 37

Y8

N9

Release related

Can host the consolidation branch

1/210

Y

Can be used for patch tracking

Y

Y

Integrates with Linaro patch tracker11

N

Y

Easy to do releases off

Y

Y

Source control/merge request/bug integration

N

Y

Community related

Easy for GCC devs to play with

Y

N12

Good visibility

Y

N13

These things don't matter:

  • Familiar to Linaro developers
  • Good place for patches that won't go upstream14

Note that there's a delay between patches going into SVN and being available for merge by the bzr import. This problem exists in both scenarios though.

  1. Harder, but all Linaro GCC devs have/need write-after-approval permission in any case (1)

  2. 'Takes a small number of minutes' (2)

  3. Some operations are really slow, some slow, but generally OK (3)

  4. Partial. MLH prefers DVCS like bzr for local branches. (4)

  5. See email from Michael Meissner via Ira (5)

  6. Pull in from the continuous bzr import at http://launchpad.net/gcc. Easy tracking back to svn revision (6)

  7. We should be working upstream then backporting. We don't at the moment. (7)

  8. Always commit to a SVN branch (8)

  9. Work should land directly upstream, then backport to the consolidation branch (9)

  10. Can't host early versions of patches that don't have the right license, copyright assignment (10)

  11. Minor. Simple to update (11)

  12. bzr checkout is too big/long; unusual tool (12)

  13. Hidden on launchpad.net (13)

  14. Everything must go upstream in the end (14)

MichaelHope/Sandbox/GCC46Hosting (last modified 2010-11-21 20:58:38)