-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix outdated repo docs #4995
Fix outdated repo docs #4995
Conversation
removing several old docs files that are no longer relevant correcting other docs that were out of date
testnet-docs: update conf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First review, please let me know if I have missed any best-practice :)
Thank you for putting this together, left a few nits and a couple general points.
Co-authored-by: Adriano Di Luzio <aldur@users.noreply.github.com>
Co-authored-by: Adriano Di Luzio <aldur@users.noreply.github.com>
* develop: (91 commits) feat: update tx estimator when tx yields too big tx error Only check if we advanced pre fork miner 2 blocks forward Fix default affirmation map settings for 3.0 chore: set 3.0 mainnet activation height chore: signers should be more permissive about a slow miner wakeup fix: use hex instead of u8 bytes in fixture Do not assume every tenure has inter_blocks_per_tenure feat: add metadata to mock signatures feat: add signer message metadata to block responses chore: convert BlockAccepted to a struct chore: fix test chore: move test chore: fix test test: verify tenure_heights in new block events chore: revert change moving request creation out of loop feat: add `tenure_height` to `/new_block` event payload chore: fix missing `clone` chore: fix log feat: various improvements to retry logic in event dispatcher feat: cap the backoff for sending events to timeout * 3 ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This PR attempts to update all docs relating to the release process for both stacks-core and stacks-signer.
Additionally, some cleanup was performed to remove files that are no longer needed (or won't be needed post 3.0) - specifically, some configs for network modes that won't be present were removed.
release process files were updated to reflect the current gitflow-ish branching strategy, with a dedicated document
./docs/branching.md
defining how branches should be named.