| Info | ||
|---|---|---|
| ||
The contents of this page has been migrated to the new developer documentation; from late on 2016-02-04 it will appear at http://developer.lsst.io/en/latest/build-ci/new_package.html. |
For DM top-level products, any new package needs to be approved before its repo is added to github.com/lsst (in an appropriate team) and it can be part of the build. Both DM-written packages and third-party packages should go through the RFC process first to confirm their name and the suitability of their contents.
DM-written Science Pipelines packages should follow the template in https://github.com/lsst/templates.
Third-party packages should be packaged as described in Distributing third-party packages with EUPS.
The new package must be added to the etc/repos.yaml file in the lsstsw package along with its corresponding GitHub URL. The version of this file in lsst-dev.ncsa.illinois.edu:~lsstsw/etc then needs to be pulled to inform buildbot where the package is located. Note that this file is governed by a "self-merge" policy; see RFC-75 for details.
The new package then needs to be added to the ups/*.table file (and possibly the ups/*.cfg file) of one or more other packages in the stack where it is used. This will ensure that the package is built as part of Continuous Integration.