You mentioned a valid point: with this PR, the binding repo and the VM repo record the versions of each other. We need to break this circular dependency. As Julia requires the version of its dependencies and we cannot change it, we probably want to remove the Julia version from this repo. This means, we need to change our CI as well.

Considering that we are under time pressure to get this upstreamed, we may prioritize getting this change approved and merged upstream.

These are what I suggest:

1. In this PR, do whatever you need for Julia, and push directly to upstream-ready/immix. Let Julia maintainers review it.
2. Create a master branch from dev for mmtk-julia. This is the branch that works with the upstream PR. We tag releases from master, rather than from dev.
3. Remove the Julia version recorded in the binding in master. We only use that version for our own CI.
4. We can remove the current CI settings for master. Once the upstream PR is merged, we will add new CI tests that pulls the Julia upstream and test with it.

We can discuss more on this tomorrow. Hopefully this can make things easier, and we do not need to figure out how the new CI should look like in this short time frame.

You mentioned a valid point: with this PR, the binding repo and the VM repo record the versions of each other. We need to break this circular dependency. As Julia requires the version of its dependencies and we cannot change it, we probably want to remove the Julia version from this repo. This means, we need to change our CI as well.

Considering that we are under time pressure to get this upstreamed, we may prioritize getting this change approved and merged upstream.

These are what I suggest:

1. In this PR, do whatever you need for Julia, and push directly to upstream-ready/immix. Let Julia maintainers review it.
2. Create a master branch from dev for mmtk-julia. This is the branch that works with the upstream PR. We tag releases from master, rather than from dev.
3. Remove the Julia version recorded in the binding in master. We only use that version for our own CI.
4. We can remove the current CI settings for master. Once the upstream PR is merged, we will add new CI tests that pulls the Julia upstream and test with it.

We can discuss more on this tomorrow. Hopefully this can make things easier, and we do not need to figure out how the new CI should look like in this short time frame.

Great idea Yi. I think that all makes sense. I'll set it all up.