Problem: patch wars in Github issues affect development

[sorpaas]

Currently there're ongoing patch wars #172, #173, #174, #122. Those affect SputnikVM's development process.

While we aim to resolve them, before they are settled, all important issues are being moved to the wiki page. This issue documents the process.

[sorpaas]

Blockchain regression process can be found at https://github.com/ethereumproject/sputnikvm/wiki/Blockchain-Regression

[sorpaas]

Memory footprint reduction process can be found at https://github.com/ethereumproject/sputnikvm/wiki/Reduce-Memory-Footprint

[sorpaas]

RPC process can be found at https://github.com/ethereumproject/sputnikvm/wiki/SputnikVM-RPC

[sjmackenzie]

Please do not use the wiki to track issues.

[sorpaas]

No Stewart, until this patch war is stopped, using wiki to track issues is a reasonable choice. Right now Github issues is just unusable.

[sorpaas]

Anyway, I'm going to close this, to prevent patch wars on this issue.....

[sorpaas]

We seemed to find a way to stop those patch wars. I'm going to reopen this issue to document the process.

[sjmackenzie]

close due to irrelevance.

[sorpaas]

Reopening this. This is so relevant to us. The patch wars started by @sjmackenzie have affected SputnikVM's development so much, and we should seriously consider abandoning C4 which is believed to be the main cause of the current problem we are facing.

[sorpaas]

Reopening this. I have no idea what's happening right now.

[sorpaas]

There seems to be something wrong with the current master branch. Until that issue is resolved, I'm going to skip using master branch by all means and use develop branch for all development and releases.

[sorpaas]

Solved by moving the repo to https://github.com/ethereumproject/esvm