-
Notifications
You must be signed in to change notification settings - Fork 75
Home
Brian Cherinka edited this page Aug 31, 2021
·
28 revisions
Welcome to the jdaviz wiki!
Jesse's rule-of-thumb:
| Points | Meaning |
|---|---|
| 13 | Full sprint |
| 8 | A bit more than half a sprint |
| 5 | A few days |
| 3 | A day or two |
| 2 | Half a day |
| 1 | An hour |
This only applies to STScI developers:
- Check if it already exists first.
- 1.1. If yes, comment on the existing issue. Stop here.
- 1.2. If no, continue to Step 2.
- Is all the info of this issue public?
- 2.1. If yes, continue to Step 3.
- 2.2. If no, continue to Step 4.
- Open issue on both GitHub and JIRA using one of the following methods:
- 3.1. If you want to utilize the nice GitHub feature/bug templates, open issue on GitHub. Then open a new ticket in JIRA and post GitHub issue URL there manually. Also apply the appropriate component label(s) on the JIRA ticket.
- 3.2. If you want to utilize the nice JIRA-GitHub integration bot (no templates), create a new JIRA ticket and remember to put
githubunderLabelsfield. Also apply the appropriate component label(s).
- Only create a new JIRA ticket without JIRA-GitHub integration bot. Also apply the appropriate component label(s). Do not use the feature described in 3.2 above. If you must have a GitHub counterpart, manually create a GitHub issue with the same title but omit all the sensitive information.
https://github.com/spacetelescope/jdaviz/pulls?q=is%3Aopen+is%3Apr+label%3Adiscussion
The mast branch of Jdaviz is a branch of Jdaviz that MAST uses for the web display of Jdaviz. The mast branch is maintained by a member of ASAB. This branch will be kept in-sync with main at regular intervals. Any new updates to Jdaviz for MAST should still come through the normal workflow of a PR from a user's personal fork, to be reviewed by the team, before merging into main. mast would then be subsequently updated. The operations (ops) environment of MAST will use a tagged release of Jdaviz.