Hi Russell,
A question for an SVN expert: how to configure the LSST DM source
repository so that major sub-components (each pipeline, the framework,
the middleware, etc) maintain their own versioning tag independent of other
DM sub-components.
The primary motivation is to enable a developer to create a new version
of a package/module without affecting the rest of the source tree in any way.
Later, other developers can integrate use of the the new release into
their own packages/modules when desired (or at a convenient time). The
existing deployment tools (pacman, eups) are currently capable of maintaining
dependency trees for each sub-component.
On the flip side, this also enables the developer working on a package/module
to select specific versions of other modules on which the package is dependent
and which need to remain stable whilst in development mode.
My initial inclination is to maintain multiple SVN repositories - one for
each *major* subcomponent. This also maps to the current reality
of developers for a module/package being clustered in close proximity.
To support the infrequent situation where changes across multiple repositories
need to be simultaneously implemented, a wrapper code could be developed to
orchestrate 'checkout' from multiple repositories and 'commit' across
multiple repositories. A post-commit step could update the version tags
in the new dependency tree. But this wrapper code is really superfluous
since it would be little more than a 'for' loop over the list of
sub-components.
What's your opinion / suggestion?
Robyn
--
Roberta (Robyn) Allsman
Large Synoptic Survey Telescope phone: 520-322-8741
Data Management FAX: 520-881-2627
4703 E. Camp Lowell Dr Suite 253 email: [EMAIL PROTECTED]
Tucson, AZ 85712 USA
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
