Stephen Mackenzie

[email protected] . Method aka Company3

I've resolved every other nerdvegas repo reference, excluding rez-shotgun which is a legacy repo still residing at nerdvegas, and omitting personal author references in changelogs and so forth. The only...

Possibly related feature request to add to discussion: Would be good to add the ability to specify that a given rez-test always runs after rez-build. Doesn't do much good when...

`test_built_package = True` seems sane to me. I mean that when I run rez-release, if the result of test_built_package (which runs the default tests as spec'd above by you) returns...

> I think the pre-release hook would install the package to a temp location first no? rez-test would use that temporary install - thus if anything fails, nothing's been released...

> 2: "rez-test mypkg mytest --interactive". Rez-env into the specified test env. I think this way of handling it (rather than via rez-env itself) is important because each test can...

Something I'm not seeing when running rez-test, is any variables that make it into the testing environ that I could use to parameterize the test from within. Such as, REZ_TEST_PACKAGE_ROOT,...

in an msys2 shell, I installed zsh, invoke zsh, and using default zsh config, installed rez and run rez-env, and I do not get any reproduction of the above stack...

I am a huge fan of semantic commit / branch naming, and allowing that semantic naming to trickle downward as helpful information. i.e, if any of the merges since the...

Is there any benefit to considering separate stable-vs-unstable release streams? (Personally, I'm in the prefer-small-releases-camp, but I'm suggesting ideas that accommodate worries from the larger-releases-camp)