Tony Kelman

@tbreloff package authors need to be responsible for dependency versioning. What features are you using, when things break how do you fix or work around them, etc. That comes with...

Yes, if something in the same environment (either an environment-level constraint or another package) has an upper bound on that package.

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...

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`

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...

This was touched on a bit in #14 (which is long and went all over the place) > > How would version resolution work on an unregistered package? Right now,...

> it's very useful to run `Pkg.clone` to try out someone's changes "cloning latest master" for development modifications or quick informal evaluation purposes will probably need to use a separate...

The scenario in https://github.com/JuliaLang/Juleps/issues/14#issuecomment-261107636 describes a situation in which upper bounds will occasionally need to be made at patch level. This would not be a common occurrence but it does...

Agreed, but that's an issue with any and all upper bounds, not so specific to granularity of major vs minor vs patch level.

> there would be less potential for confusion and problems if package management operations don't actually take place in the current process Why, exactly? What problem does this solve? If...