The new code is now running on testnet, and is undergoing changes. There are
some features which have been removed to allow release on time. After release
there are going to bugs, and probably even serious issues. There will be some
which happen immediately and I am sure there will be fixes needed after 1-2
months.
I would think so too. Anyway, the features that have been left out (bond market)
will not directly cause any trouble ..
1. Who does that maintaining?
Depends. If the implementation does not behave as documented due to a bug, then
the devs will have easy time convincing witnesses to upgrade to an updated
version of graphene and have a hard fork.
However, if it turns out that something else (maybe bit assets or who knows
what) does not work as desired but works as documented .. then the devs will
have to propose a changing hardfork and let shareholders vote for the hardfork
..
Eventually, when the implementation is stable, devs will have hard time FORCING
any hard forks ... they will all require shareholder approval.
2. What happens to the features which are being removed for now?
At least for the bond market, I am pretty certain that it will appear in
BitShares 2.1. They will be implemented by whoever feels fit and delivers the
suited upgrade. Then shareholders will (or will not) give approval at which
point the blockchain will upgrade (itself
)
I know everyone is excited about the new release but I want to find out what is
the exact roadmap immediately after release as that influences my trading
decisions.
In the last hangout the dev said that there will be a testnet with the same
genesis block. Will that testnet be released before the mainnet? WIll I be able
to access that by using a testnet flag? I think it would be better if the
testnet was allowed to run for a few days before the main release so that any
critical bugs are discovered, and the exchanges are able to test integration.
The testnet chain will have a different prefix (GPH and not BTS) for all
addresses and keys. It will also have a very different chain-id which can be
used as a flag to the client to choose the chain.