https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INFRA-38 Software Development Infrastructure <p>Our coding standards and development procedure are derived from LSST's. In many cases, we can use the relevant LSST documentation directly; in others, some modification may be appropriate.</p> <p>Collect and publish a collection of pointers to the relevant LSST docs, together with such modifications as are required for PFS DRP.</p> INFRA-38

Document coding standards and procedures

Bug Major Done Done swinbank swinbank Fri, 1 Jul 2016 19:17:16 +0000 Sat, 30 Jul 2016 18:40:09 +0000 Sat, 30 Jul 2016 18:40:09 +0000 0 2 <p>Attached is a set of notes I brain-dumped on how things work on LSST and how they translate to PFS. I do not claim it is comprehensive, but it's a starting point. Can you please check and see if there's anything in there you disagree with and/or if there are important things that ought to be added?</p> <p>Because of the way PFS-JIRA is configured, it's only possible to have a single user named as a reviewer. Changing that is not impossible, but it's awkward. Therefore, only <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=aritter" class="user-hover" rel="aritter">aritter</a> is named as a reviewer here, but I think it would be useful for <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl" class="user-hover" rel="rhl">rhl</a> to take a look as well.</p> <p>Looks reasonable and captures everything I can think of.</p> <p>Now displayed at <a href="http://pfs-2d-pipeline.readthedocs.io/en/latest/dev.html" class="external-link" rel="nofollow">http://pfs-2d-pipeline.readthedocs.io/en/latest/dev.html</a>.</p> Development Epic Link INFRA-35 Rank 0|02qpuc:zx Reviewers aritter Sprint 2014-15 2014-16