Milan Kolar

> This may be too complicated but how about publishing two versions and link them as dependent? we've decided to do something similar. We'll create a new type called `masterversion`...

We've implemented this in the [pypeclub fork](https://github.com/pypeclub/avalon-core/pull/110) of core. From testing so far it looks very useable, albeit we'll still be recommending our clients not to use it unless the...

We only made a rudimentary version for nuke so far that gathers latest relevant publishes, loads them all and connects what is possible. Not very robust, but it is a...

>What Milan describes does sound different from what the issue itself describes originally, but I can see how that might fall under scene setup. However what he describes I think...

Reading through the discussion I'm leaning on the side of storing full path to the work directory as `AVALON_WORKDIR` or something similar and application's name as ` AVALON_APP` (the name...

This is great. The only thing I'd change would be trying to display it as node graph to make it clearer how the data flow, but that's just a UI...

I like it. @antirotor what do you think in respect to unreal for example?

To be perfectly honest, we didn't find time to test this properly. Code wise it looks very nice, but we were swamped and couldn't afford the time to test. I'm...

To add to this somewhat. We need to connect Premiere and eventually other adobe applications to avalon. Because they don't run python we were looking for an elegant solution and...

we are using it at one site. However we didn't have capacity to spend some good time on it, so it's a bit temperamental and not very stable.