New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

H14 -- asset re-saving PROTOCOL :) #300

Closed

johnnyquest opened this issue Jan 17, 2015 · 1 comment

Labels

MUCHO IMPORTANCIA

Contributor

johnnyquest commented Jan 17, 2015

warnings are mostly about missing H13 parameters
everything should be resaved in H14
- make sure all still works in H13, though (shouldn't be a problem)
- emphasis on H14, but all assets should be warning-less in H13, too
- always mention the H14 resaving in both the asset's Release Notes and the github commit
- after resave, always check if it still works in H13 (e.g. test with an example scene -- a good incentive to make some more examples, maybe :DDD)
  - (it's unreasonable to test this on a regular basis, but at least once it should be done)
- ...
it's still a valid bug report if something doesn't work in H13
most of our assets are pretty much version-agnostic (to a degree), but...
the nodes are we absolutely rely on are: wranglers, python script (s)op.

johnnyquest added MUCHO IMPORTANCIA perpetual labels

Contributor Author

johnnyquest commented Aug 27, 2016

we'll assume H15 as baseline

johnnyquest removed the perpetual label

johnnyquest closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment