Move js & js-old code to github.com/parity-js

[jacogr]

So long and thanks for all the fish.

• Move js code to github.com/parity-js into separate repos
• Updated shell & wallet references with cargo update -p parity-ui
• Tested operation of UI with cargo build --release --no-default-features --features ui
• Update CI scripts to remove js-build & js-release

cc @amaurymartiny @ngotchac @tomusdrw

[jacogr]

This auto-gen line looks funny. (And the next one - not sure how/why there are 2 refs? Or rather what I assume to be refs)

[tomusdrw]

It's because you have set explicit rev in Cargo.toml file. Instead you could just set up github repo and let Cargo.lock maintain the revision.
But it's fine, might be a bit more pain in the ass to update though:

1. edit Cargo.toml
2. Run $ cargo update -p parity-ui-dev

vs

$ cargo update -p parity-ui-dev

[jacogr]

100%, bit more of a pain with the revs - this does feel safer since the shell will morph as we get closer to having it dapp-able.

(e.g. @amaurymartiny is working really hard on allowing the shell to be able to run as a dapp & Electron app #next branch in that repo, if that goes to main it should already be fully removed from the 1.10 binary, but if not it is just easier to manage having a compatible know version based on rev)

[tomusdrw]

Looks good, how do we plan to update the revisions though?

[tomusdrw]

It's because you have set explicit rev in Cargo.toml file. Instead you could just set up github repo and let Cargo.lock maintain the revision.
But it's fine, might be a bit more pain in the ass to update though:

1. edit Cargo.toml
2. Run $ cargo update -p parity-ui-dev

vs

$ cargo update -p parity-ui-dev

[jacogr]

Updating will have to be done manually, i.e. like we do for other packages anyway.

We can still push from the Travis build for the shell & wallet to update the refs, but since we want to not have Parity (1.10) build the UI in, I would rather just update manually when we need to since it is not long-term. (But if need be, can just push from CI again)

[debris]

I have no idea why 'js' report is requried. @5chdn is it because of our github repo settings?

[jacogr]

@debris it was changed on the repo settings by @5chdn - should be fine now.