Hi there!
Jan Holesovsky wrote:
[... snip ...]
Unfortunately, SVN does not serve our (= people around ooo-build)
needs :-( [CVS even less, of course.]
What we need is a tool that allows us to have a modified codebase (ooo-build)
while we are still able to contribute the modifications back to up-stream
easily. Today we solve it with huge amount of patches (~1000), we have to
create CWS'es from that, and it's becoming hard to manage, especially with
big features like the VBA interoperability or cairo canvas. DSCM is so far
the most suitable way these days (and git in particular seems to be the
best).
Well, why not just have an ooo-build ChildWorkspace which never gets
integrated as some kind of ooo-build-Release-ChildWorkspace regulary
"cwsresync" that one to newly available masterworkspaces than develop
new features on ChildWorkspaces and join in Changes from big feature
ChildWorkspaces like that cairo canvas with commands the SCM offers into
that ooo-build ChildWorkspace. Even today it´s quite easy to join
changes from one ChildWorkspace which is not yet integrated into another
one with relative simple CVS commands. The ooo-build env could provide
some tooling to do these joins. This should be doable with any kind of
SCM we´d use as we would have to adapt that CWS tooling we use above the
actual SCM of the future. So commands like cwsresync will still be there
after a switch.
Or well even better why not just wait with releasing big features in
your builds until their ChildWorkspaces got integrated into the Master
just like anybody else does ;-) - I really did never really understand
that "special" needs of people around ooo-build completely ;-)
Kind regards,
Bernd Eilers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
