3.4.3 Saving a version
To commit the current state as a version, select your Working
Version, enter a Version number (free-form) and comment, and press
Save
Version. MetaEdit+ will check that the version number and comment are not
empty, and that the version number is unique, and let you correct them if
necessary. Your transaction will be committed and a new transaction and version
will be started. If your MetaEdit+ license includes the API features, you may
configure MetaEdit+ so Save Version performs additional actions to integrate
with an external Version Control System: see Section
3.5.4.
In a multi-user situation, it is useful to also be able to
make a version where no other users have unversioned changes; to do this, ask
others to version, set
Save as Release, and press
Save Version. This ensures that all changes in the repository (and
visible in the graph and metamodel snapshots) are part of a version that is
closed and hence commented. It will also optimize the storage of graph snapshots
by merging duplicate snapshots across users, slightly speeding up comparisons.
The space thus freed will be recovered after repository Garbage Collect (see the
‘MetaEdit+ System Administrator’s Guide’), which itself
performs the same optimization.
Once a version has been saved, its version number and the
comments within it cannot normally be changed. If you do need to change one, you
can choose
Allow Changes from the pop-up menu in
that field;
Commit makes the change permanent. (Note that if you are
integrating with an external VCS, this will not update it, so you should make
the same change manually there
too.)