Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
bigchaindb/Release_Process.md
libscott 8343bab89f Schema definition (#798) 
Commit messages for posterity:

* wip transaction schema definition
* test for SchemaObject
* test SchemaObject definions meta property
* schema documentation updates
* test for basic validation
* commit before change to .json file definiton + rst generation
* move to straight .json schema, test for additionalProperties on each object
* add asset to transaction definiton
* remove outdated tx validation
* make all tests pass
* create own exception for validation error and start validating transactions
* more tx validation fixes
* move to yaml file for schema
* automatic schema documentation generator
* remove redundant section
* use YAML safe loading
* change current_owners to owners_before in tx schema
* re-run tests and make correct yaml schema
* fix some broken tests
* update Release_Process.md
* move tx validation into it's own method
* add jsonschema dependency
* perform schema validation after ID validation on Transaction
* Release_Process.md, markdown auto numbering
* remove old transaction.json
* resolve remaining TODOs in schema docuementation
* add `id` and `$schema` to transaction.yaml
* add transaction.yaml to setup.py so it gets copied
* address some concernes in PR for transaction.yaml
* address more PR concerns in transaction.yaml
* refactor validtion exceptions and move transaction schema validation into it's own function in bigchaindb.common.schema.__init__
* add note to generated schema.rst indicating when and how it's generated
* move tx schema validation back above ID validation in Transaction.validate_structure, test that structurally invalid transaction gets caught and 400 returned in TX POST handler
* remove timestamp from transaction schema index
* Add README.md to bigchaindb.common.schema for introduction to JSON Schema and reasons for YAML
* Use constant for schema definitions' base prefix
* Move import of ValidationError exception into only the tests that require it
* Move validate transaction test helper to tests/common/util.py
* move ordered transaction schema load to generate_schema_documentation.py where it's needed
* use double backticks to render terms in schema docs
* change more backticks and change transaction version description in transaction schema
* make details a mandatory property of condition
* Many more documentation fixes
* rename schema.rst to schema/transaction.rst
* Fix documentation for Metadata
* Add more links to documentation
* Various other documentation fixes
* Rename section titles in rendered documentation
* use  to manage file handle
* fix extrenuous comma in test_tx_serialization_with_incorrect_hash args
* 'a' * 64
* remove schema validation until we can analyze properly impact on downstream consumers
* fix flake8 error
* use `with` always
2016-11-22 11:17:06 +01:00

1.5 KiB
Raw Blame History

Our Release Process

This is a summary of the steps we go through to release a new version of BigchainDB Server.

  1. Run python docs/server/generate_schema_documentation.py and commit the changes in docs/server/sources/schema, if any.
  2. Update the CHANGELOG.md file
  3. Update the version numbers in bigchaindb/version.py. Note that we try to use semantic versioning (i.e. MAJOR.MINOR.PATCH)
  4. Go to the bigchaindb/bigchaindb Releases page on GitHub and click the "Draft a new release" button
  5. Name the tag something like v0.7.0
  6. The target should be a specific commit: the one when the update of bigchaindb/version.py got merged into master
  7. The release title should be something like v0.7.0
  8. The description should be copied from the CHANGELOG.md file updated above
  9. Generate and send the latest bigchaindb package to PyPI. Dimi and Sylvain can do this, maybe others
  10. Login to readthedocs.org as a maintainer of the BigchainDB Server docs. Go to Admin --> Versions and under Choose Active Versions, make sure that the new version's tag is "Active" and "Public"

After the release:

  1. Update bigchaindb/version.py again, to be something like 0.8.0.dev (with a dev on the end). This is so people reading the latest docs will know that they're for the latest (master branch) version of BigchainDB Server, not the docs at the time of the most recent release (which are also available).