Skip to content

Instantly share code, notes, and snippets.

@JeanChristopheMorinPerso
Last active April 6, 2023 20:17
Show Gist options
  • Save JeanChristopheMorinPerso/25b6c3d4185931d52b247f35c7a0ac5f to your computer and use it in GitHub Desktop.
Save JeanChristopheMorinPerso/25b6c3d4185931d52b247f35c7a0ac5f to your computer and use it in GitHub Desktop.
Rez development experience

This document lists some ways that we could improve the experience of developing rez.

Tests

  • rez-selftest vs unittest vs pytest, etc.
  • Coverage isn't working in CI.
  • rez-selftest is annoying.
  • Better coverage
  • Split unit tests and integration tests.

CI

  • Windows is really slow (even with docker because the iamge is quite big).
  • One workflow per platform makes it harder to work with.

Code

  • Linting + code formatting would help. We do have a linter but I think it could be improved.
  • We should remove any unused code.
  • Define public API.
  • Concepts should be clarified.
  • Compatibility policy: Which part do we garantee will stay compatible and which part can we sometimes break (when we have a good reason)?
  • Deprecation policy: How can we deprecate things? There is a lot of old stuff in rez that are "deprecated" but still there. We need to find a way to eventually get rid of deprecated stuff.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment