How to restore previous module baseline to current revision?
One answer
Unlike a single artifact, the module is essentially a collection of many artifacts. If we are to "restore" the module to an older version, what are we going to do with the module artifacts added after the baseline was taken? Delete them or leave them there as orphans? So even you consider an RFE, you need to make it clear how you would like it to be implemented.
If you just want to work with an older version of the module, you can "copy" the baseline as a new module. Of course you will get a set of new IDs which may not be desirable.
If you just want to work with an older version of the module, you can "copy" the baseline as a new module. Of course you will get a set of new IDs which may not be desirable.
Comments
Robert Huet
Jul 14 '14, 11:41 p.m.Thanks, Donald, you bring up a good point. I will discuss this with my customer about creating an RFE. Intuitively, I would expect the system to inform the user and let them decide whether to delete the new requirements or save them somewhere else.
Stef van Dijk
FORUM MODERATOR / JAZZ DEVELOPER Aug 01 '14, 6:37 p.m.Additionally, I think it's more than just a concern about added or removed artifacts since the baseline. What if the underlying core artifact has changed? Do you also revert the state of the core artifacts (which may be used in other modules or independently) when reverting the module? I imagine it's issues like these that are why this is not yet implemented and might be something being investigated for the Configuration Management (CM) currently in beta.
1 vote
Robert Huet
Aug 04 '14, 1:52 p.m.Makes sense. Thanks for the additional insight!