Add a place to track various BIP9 deployment proposals.
As per IRC meeting http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.2016-05-05-19.01.html
Add a place to track various BIP9 deployment proposals.
As per IRC meeting http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.2016-05-05-19.01.html
ACK b56f7d7b6da75a31acfff42a678ed31b0555259f
I think it would be better to format this as a table from future to past (rows, each being a year, or quarter-year), and bits (columns). Probably don't need testnet.
0 | @@ -0,0 +1,37 @@ 1 | +==Deployments== 2 | + 3 | +List of proposed deployments. 4 | + 5 | +State can be defined, active, failed. Dates are in UTC. 6 | + 7 | +{| class="wikitable"
Unfortunately it seems class="wikitable sortable" won't render on GitHub.
seems to render ok https://github.com/btcdrak/bips/blob/bip9assign/bip-0009/assignments.mediawiki what am I missing?
Luke was suggesting to sort the table and the best way to do this would be dynamic. (i.e. adding the sortable keyword). The actual mediawiki parser understands sortable but the github parser does not, I think.
afaic, none of the fancy stuff works on Github rendering. Look at the README.mediawiki for example - it's got lots of formatting and colours in the markup, but doesnt render.
I'm not suggesting to merely sort it, but to format it in a way that it is clear which bits are used at what times.
That's slightly complicated since bits will become free earlier than expiry once activated. Maybe we should keep it simple... or simply strikeout the bit once activated?
ACK, thanks, I was about to do this but you beat me to it by almost a week :)
I think having testnet in there is fine