Comments (6)
There should probably be a test-only manifest file, or a test-only section of the main manifest file. test/REQUIRE
should be made more capable the same way as REQUIRE
from juleps.
I think this is better handled by staged tags. Nothing should depend on "master," that's a moving target and bad for reproducibility. If you depend on an unreleased sha, then you're not testing against what your users will be installing once it gets released. So this is inherently a temporary thing, and would be better handled by directing the test version of the package to use a test registry to get its dependency version info. Then if the changes from the test registry make it through as is to the release registry, you're testing the same thing users will get.
from juleps.
Nothing should depend on "master," that's a moving target and bad for reproducibility.
Yes, for tagged versions I agree. But that's irrelevant. But I was wondering if it can be standardized how/where branches are chosen for testing. When checking someone's master or dev branch, this stuff can be hidden: it's some script called in the .yml, or sprinkled into the master for the tests. It's up to the developer to pull this all out / comment it out when changes in downstream packages occur and when you eventually want to tag. But it also means that this information is scattered around the repositories if you're trying to find out how to get some development branch working. If it was just in the test/REQUIRE file how everything is being tested, it would be clear (and it would be clear that everything needs to be testing on releases for any tag).
from juleps.
There could be test/{Config,Manifest}.toml
files corresponding to the current test/REQUIRE
.
from juleps.
if we're using a richer format here, then no need for it to be a separate file really. there would be some advantage to recording test dependency info in the registry for a package as well, so all that information is available without having to download every version of every package to get it
from juleps.
True, it can simply be a separate section. There's space for various kinds of targets but I'm unclear on the design there. @wildart had some thoughts on it so perhaps he can chime in here.
from juleps.
Related Issues (20)
- Pkg3: "Binary" or "non-source" packages HOT 9
- Pkg3: Unregistered Packages? HOT 2
- github private with git credentials
- Pkg3: telemetry HOT 5
- Pkg3: relative paths for adding local packages HOT 3
- Don't use semantic versioning for Pkg3 HOT 10
- Pkg3: TOML Compatibility HOT 4
- package alternatives in Pkg3? HOT 18
- Package options HOT 9
- Progress display? HOT 3
- Pkg.add(pkg) when pkg is installed HOT 6
- Pkg3: naming of project filenames HOT 20
- Pkg3: Quality Tags (unstable/testing/candidate/stable) HOT 1
- Pkg3: developing packages HOT 3
- Find Julep: issue with sentinel values HOT 26
- Pkg3: comparison with Guix HOT 2
- Deprecation Julep HOT 12
- Branching process Julep HOT 1
- Release process Julep HOT 2
- Python to Julia transpiler HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from juleps.