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-46 Software Development Infrastructure <p>Set one project as tracking of instrument control software development with configuration records and changes tracking. We already have SCAM project for camera module configuration tracking, and will reuse this as "Instrument development" with "INSTRM" key.<br/> Also delete (or just close; no comment posted yet) <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1" title="All the work involved in reading out the HgCdTe H4RG devices" class="issue-link" data-issue-key="INSTRM-1"><del>SCAM-1</del></a>, <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-2" title="All the work involved in reading out CHARIS&#39;s HgCdTe H2RG device" class="issue-link" data-issue-key="INSTRM-2"><del>SCAM-2</del></a>, which is for H4RG readout development which will not be in this JIRA instance.</p> INFRA-46

Reuse SCAM as tracking ICS development "INSTRM"

Task Major Done Done shimono shimono Thu, 28 Jul 2016 06:11:23 +0000 Mon, 12 Dec 2016 17:35:11 +0000 Wed, 9 Nov 2016 07:27:20 +0000 0 2 <p>Not enough technical evaluation has done (could not take enough time to do), but no heavy pre/post works are listed, it seems system technically this change should work well and smooth.</p> <p><a href="https://confluence.atlassian.com/adminjiraserver071/editing-a-project-key-802592377.html" class="external-link" rel="nofollow">https://confluence.atlassian.com/adminjiraserver071/editing-a-project-key-802592377.html</a><br/> <a href="https://answers.atlassian.com/questions/200230/" class="external-link" rel="nofollow">https://answers.atlassian.com/questions/200230/</a></p> <p>Project name/key changed and <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1" title="All the work involved in reading out the HgCdTe H4RG devices" class="issue-link" data-issue-key="INSTRM-1"><del>INSTRM-1</del></a>, <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-2" title="All the work involved in reading out CHARIS&#39;s HgCdTe H2RG device" class="issue-link" data-issue-key="INSTRM-2"><del>INSTRM-2</del></a> has marked as WONTFIX.</p> <p>Sorry, but I really don't like putting camera detector and electronic problems in with general software development. I think that detector&amp;readout problems merit more than component tags or labels, partly because they will be treated quite differently, and will be handled by different people. Also, some will never be fixed but should be tracked.</p> <p>Also, some H4 detector issues will not be covered by ITAR, and so can be kept with CCD issues.</p> <p>I guess we could simply mark CCD, ADC, FEE, FPGA, H4, ASIC, SAM issues with those component tags or labels, but I'd still vote for keeping them in a separate project.</p> <p>I missed your comment <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>.<br/> For now, we define the same workflow, screen items, permission over all projects, and only changes are project roles (but mostly not used). So, I don't think we gain something more than having component to categorize these, with having separate project. We also may define separated sprint if we want to do for some special period like mass gathering for pre-ship review, etc.<br/> We may have interactions between detector control tickets and other parts, by such as FITS header definition put from other parts, SpS AIT, and it may be better to be kept in the same project.</p> <p>File new ticket, if you really want to propose to have.</p> Development Epic Link INFRA-43 Rank 0|ii00lr: