Building a proper framework for evaluation and acceptance of new package into desc-python
@heather999 is already working on this.
Since Dec 11, 2020.
Assessment
This issue has not been assessed yet.
Description
we need a proper way to solve issues like https://github.com/LSSTDESC/desc-help/issues/53 by providing the collaboration with an efficient way to evaluate adequacy of a dev package for integration into the DESC ecosystem, and a more organized way to build the path to acceptance.
One easy enough possibility is to build on the actions of this repo to propose a sequence to developers : branch desc-python, modify its actions so as to trigger CI on the new package, and push with CI triggered on push. We can envision different level of CI depending on push to branch, pull request to bleed or to master, etc...
This would not solve for all the things that need to be properly checked by developers, and certainly not the algorithmic correctness, but at least: 1/ this will provide a wiew into proper install at the time of the pus and pull requests, 2/ we can check dependency consistency, like tagged versions of other packages 3/ we can triage the pull request and iterate with much better clarity on purpose/scope/unit testing, in some cases the tests dir will be available and pytest can be triggered in the CI, and we can propose a differential level of scrutiny between bleed dev and the final acceptance in the production version.
comments and thoughts most welcome
- Dominant language
- Shell
- Stars
- 7
- Forks
- 3
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LSSTDESC/desc-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
LSSTDESC/desc-python#192 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LSSTDESC/desc-python#187 ·
-
create txpipe branchPossibly taken @heather999 claimed this 23 days ago. Open
LSSTDESC/desc-python#188 · 1 assignee ·
-
temporarily restrict astropy<8.0.0May be free again @heather999 claimed this 75 days ago, and no pull request is open. Open
LSSTDESC/desc-python#185 · 1 assignee ·
-
Temporarily restrict pzflow < 4.0.0May be free again @heather999 claimed this 116 days ago, and no pull request is open. Open
LSSTDESC/desc-python#182 · 1 assignee ·
All issues in LSSTDESC/desc-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
YosysHQ/oss-cad-suite-build#216 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ekalinin/github-markdown-toc#167 ·
-
out-of-date
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CachyOS/CachyOS-PKGBUILDS#1917 ·
Maintainers usually reply within 1 day
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day