Instead, it is better practice to keep version comments as
part of the models, either as a visible object or as a property of the model. This is of
course a practice familiar to many from programming, and brings the added bene?¬?t
that the version history remains part of the model, even after export and import to
another repository. The individual model version comments since the last repository
version can easily be collected by a generator as the comment for the version of the
whole repository.
15.3.5 How Does It Work in Practice?
Our experience is that versioning has simply been a nonissue in all the projects we
have worked on. Of the material in this chapter, customers ask far more questions
about how to build modeling languages and models effectively to allow reuse. Most
customers have simply zipped up the repository for storage in version control, as
version control systems generally require a versionable unit to be presented as a
single ?¬?le.
Where customers have decided to use a multiuser repository, the only issues
encountered were technical ones during installation, for example, how to help
406 DSM IN USE
customers correct name server miscon?¬?gurations within their organization so that
client computers could communicate with the repository server. Where customers
opted for single-user repositories, a single feature, application, or project was
assigned to a single developer and stored in a single repository.
Pages:
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786