This repository was archived by the owner on May 23, 2023. It is now read-only.
This repository was archived by the owner on May 23, 2023. It is now read-only.
Fix the develop branch #373
Description
Right now, develop builds look dire. In order to get a green light again, I think (at least) the following steps need to be done:
- merge Switch to the latest version of
fixtures#372 to fix the test-fixtures - rebase and merge Fix for the issue #370 #371
- rebase and merge Piper/fix block tests invalid state #369
- identify and fix outstanding bugs recently introduced
- restart from last working develop and cherry-pick good commits into
fix-develop - move new feature commits/EIPs into branches PRs of their own, based on
fix-develop, so they can be fixed/merged atomically; create PRs againstfix-develop:-
EIP 90 EIP 90 #379metropolis_config Add metropolis config #383 ✔️ - EIP 86 EIP86 #377 ✔️
- EIP 98 EIP 98 #378 ✔️
- EIP 100 EIP 100 #380 ✔️
- general py3 stuff More py3 fixes #386 ✔️
- DAO HF
# 382Possible DAO HF impl for reference #387 ❔ (no tests for that) - VMExt
# 384Further VMExt abstraction #388 😢 - EIP 97
# 381EIP 97 #389 😢
-
- ? force push
fix-developontodevelopafterwards (
Q: is there a nicer way?
git checkout develop git checkout origin/fix-develop . git checkout develop git commit # ae2498ac7f907dddc819185c013e9931228704d3 git merge origin/fix-develop # 025d43b7377a781be2e6d6c0ead5a7fb59bb6135
^--- thanks @ulope !
Please everyone involved in above PRs organize through this issue, so we have a happy travis guy and a ✅ again soon!
Metadata
Metadata
Assignees
Labels
No labels