mirror of
https://github.com/hydrosquall/tiingo-python.git
synced 2026-02-01 17:04:18 +01:00
Add New Release notes
This commit is contained in:
@@ -105,6 +105,12 @@ Before you submit a pull request, check that it meets these guidelines:
|
||||
https://travis-ci.org/hydrosquall/tiingo-python/pull_requests
|
||||
and make sure that the tests pass for all supported Python versions.
|
||||
|
||||
|
||||
Release Procedure
|
||||
-----------------------
|
||||
|
||||
See RELEASE.rst .
|
||||
|
||||
Tips
|
||||
----
|
||||
|
||||
@@ -125,4 +131,3 @@ In order for py.test to run, you will have had to create an environment variable
|
||||
However, now this api key will become embedded in the test fixture file that is created per the prior procedure. In order to remove this api key from the new test fixtures, run the following from the top level directory::
|
||||
|
||||
$ ./tools/api_key_tool.py
|
||||
|
||||
|
||||
13
RELEASE.rst
Normal file
13
RELEASE.rst
Normal file
@@ -0,0 +1,13 @@
|
||||
============
|
||||
Issuing New Releases
|
||||
============
|
||||
|
||||
Tiingo follows semantic versioning (semver.org) practices.
|
||||
|
||||
The following shows how to make a release for version 0.8.0
|
||||
|
||||
1. Make a branch called release/0.8.0
|
||||
2. Ensure HISTORY.rst (the Changelog) is up to date
|
||||
3. Update __version__.py to 0.8.0
|
||||
4. Open a merge request to master
|
||||
5. After the merge request is approved and merged, tag and push the merged commit with 0.8.0. Travis CI will be responsible for releasing the new code to PyPI.
|
||||
Reference in New Issue
Block a user