Re: [platform-core-dev] Re: multi-stream/rollup support

[Ed Warnicke <eaw@xxxxxxxxx>]

Thomas L Roche wrote:
<snip />

> Yes. We maintain separate workspaces in order to contain the
> uncertainty: after patching each workspace, we can compile and test in
> it. I would like the platform to automate the patch process as much as
> possible. Can you suggest additional or alternative function(s) toward
> this end?
>
>  
I think we share a common problem...

We use task branches to all work (pulled from other
integration branches).   When a task is completed
it's changes are commited back to the integration
branch.  If we need to cross-commit, a task branch is
pulled against each additional branch to which we
need to cross-commit (ie, a new project is created)
and the patch is applied.  Then each of these new task
branches is tested and finally commited to their
parent integration branch.

Auto patching would be great.  But I've also been thinking
thoughts about 'dependent' workspaces.  In the example
above, each of the workspaces created just to receive
a cross-commiting patch is 'dependent' on the projects
in which the work was originally done.  It would be
nice to be able to see that dependency, and to in some
fashion roll-up the dependent projects so that a
developer could focus on the top level tasks they are
performing without swimming in a see of pending
cross-commit projects.

Thoughts?

Also, with Eclipse generally (AFAIK) working over one workspace
at a time, how is cross workspace autopatching going to work?

Ed

> _______________________________________________
> platform-core-dev mailing list
> platform-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-core-dev
>