Modest Changes to the organization of EOS.IO Github issues
Heads up if you're tracking the EOS.IO Github -- yesterday we rationalized the mapping of issues to milestones, reflecting that our work is now proceeding in two tracks, as well as our go-forward standard of only placing an issue in a milestone when it clears testing at the end of a sprint. We've also completed setup of sync between Jira and Github, so we moved some Github issues to new issue numbers as a side effect. (You'll see our Jira ticket numbers as a prefix in the Github issue title.)
Leave Modest Changes to the organization of EOS.IO Github issues to:
Best Posts From Thomas Cox
We have not curated any of thomasbcox's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From Thomas Cox
- EOS.IO - why letting block producers pay you for your vote is harmful
- A Response to Kai Sedgwick
- Changes to the forecasting of EOS.IO Software development
- 10^6 Blocks on EOS.IO Dawn 2.0
- Incentivising Voting - when, how and by whom
- Welcome to EOS Governance
- Modest Changes to the organization of EOS.IO Github issues