Riak MDC Replication
- manual verification of code
- eunit (w/ gist of output)
- EQC (w/ gist of output)
- riak_test (w/ gist of output)
- Dialyzer
- XRef
- Coverage reports
- internal docs (design docs)
- external docs (docs.basho.com)
- man pages
- design documentation + diagrams
- nothing formal
- to help out during support, "this is how xyz works"
- eunit tests
- riak_tests
- EQC + Pulse tests
- tests at scale and under heavy load
- Boston Cluster or AWS
- notes for public documentation
- for the docs team
- git tag the specific commit(s) that will be released
- run all eunit tests, EQC tests, store the output in a gist.
- if possible, run all riak_tests for replication
- record specific commit(s) that the beam targets in a README.txt file
- create a tar file.
- Note that OSX will include a hidden directory in the tar file. Find the knob to prevent those files from being added to the .tar file, or build/test the beams on Linux. (you can use 'find' to pipe the exact files you want into the tar, see: https://github.com/basho/node_package/blob/develop/priv/templates/fbsd/Makefile#L27 for an example of using -rf with a pipe)
- include the README.txt file from the step above
- once .tar is built, calc an MD5 to pass along with the file
- create an entry on https://github.com/basho/internal_wiki/wiki/Releases page
- include:
- link to the gist output
- version of Erlang the beams were built with
- MD5 of the file
- link to compiled beams
- include:
- notify client services + TAMs
- port the PR to the
develop
branch if applicable