The slip down memory lane

[Kevin Kofler]

Nathanael D. Noblet wrote:
> Just an idea, without _fully_ understanding the infrastructure, man
> power etc ramifications.
> 
> Since the move to git, would it not be easier to allow features to
> branch rawhide, get their individual bits together (syncing with 'trunk'
> periodically)... Then like the kernel does, merge back the working bits
> to rawhide for the alpha. Which would essentially then be making sure
> that the features that were merged in play nice together?
> 
> Each approved feature gets a branch of what would be rawhide, they can
> do their thing insulated from others till they are ready, like the
> python stuff, having all the packages built aside till they are all
> ready, and then being merged into rawhide when they are ready and
> tested...

The problem is, if they're more than one change requiring a partial or total 
mass rebuild (e.g. Python and Boost which both required many rebuilds for 
dependencies), the sets of packages to rebuild often intersect (and for 
Python and Boost, they did, in fact even Boost itself needed to be rebuilt 
for Python), complicating that process.

        Kevin Kofler