Can we have multipe versions of a Mashup and eventually merge them back into one?
Question posted 4/7/09 by Stephane Venne
I have a little question.
Here at my work we are preparing to have multiple developers working on our dev server.
So far so good, he can check out and check in stuff.
But my problem is that I know that in the future that we will not only have to work in the same mashup, but also that we will have to work on different version, parallels ones that will need eventually to be merged.
For example let’s say we get to request for changes on the same mashup. The 2 improvement might not be released at the same time and the last one released will have to include what the previous one had, so it’s like a merge but not exactly like one just go one way.
Is there a way to clone a mashup on the same server then at one point have it merged back?
Comment posted 4/8/09 by Brian Rosenberger
we currently neither support branching the mashup version tree nor merging changes from other versions. However you may come near to that if you set up two mashup manager instances (with to different databases attached), you can handle each branch in one of those repositories.
But BE WARNED. This is not a supported or verified set up. You have to take care of any changes (collisions) yourself.
Make sure to request an enhancement for branching the mashup version tree.
Comment posted 4/8/09 by Stephane Venne
I think i'll learn to live without, thanks for the speedy response.
Maybe in the future i'll try the to manager instances, sound interesting