[x] ERC20 has been stalled for a long time, what is the plan for this?
A: for now we keep it in the codebase but disable it in production
[x] 3Bot Registration/Record-Management was implemented a very long time ago, in the meanwhile however specs and requirements have changed:
A: for now we keep it unchanged, but disable it in production
[x] Should this still be part of tfchain?
~Does it need to use the generic digitalrecord plugin, planned for Rivine?~
~If so, are we OK that we cannot validate anything that we currently do validate?~
~what needs to be updated? e.g. the requirements as well as what is considered a valid 3Bot name seems to have changed, yet none of these requirements are reflected in the actual tfchain consensus code~;
Further:
[x] We have not made a production release since October of 2018 (1.1.1), yet we have quite some fixes and improvements to the CLI, daemon and explorer frontend code. It would be great if these could be live in production so people can start enjoying these fixes/improvements;
A: a release will be made
[x] We have not made a testnet release since January of 2019 (1.1.2-rc1), yet a lot improvements/fixes have been happened since to the CLI, daemon and explorer frontend code. This makes it that people report bugs that have already been fixed. As testnet is supposed to be the latest code I think we can just make a new RC2 Release (and ship it);
GlenDC
commented
5 years ago
Further:
1.1.1), yet we have quite some fixes and improvements to the CLI, daemon and explorer frontend code. It would be great if these could be live in production so people can start enjoying these fixes/improvements;1.1.2-rc1), yet a lot improvements/fixes have been happened since to the CLI, daemon and explorer frontend code. This makes it that people report bugs that have already been fixed. As testnet is supposed to be the latest code I think we can just make a new RC2 Release (and ship it);