CityOfZion / neo-python

Python Node and SDK for the NEO 2.x blockchain. For NEO 3.x go to our successor project neo-mamba
https://neo-python.readthedocs.io/en/latest/
MIT License
313 stars 189 forks source link

Updating development version #1023

Open lapetina9 opened 4 years ago

lapetina9 commented 4 years ago

Updating development version because the documentation link is pointing to development, not to master branch, where changes were made.

@ixje, the documentation website directs to the information in the development branch. Should we leave it like this? Or should we change it?

What current issue(s) does this address, or what feature is it adding? The documentation is using the development version (branch)

How did you solve this problem? I want to send the changes to the development branch

How did you make sure your solution works?

Are there any special changes in the code that we should be aware of?

Please check the following, if applicable:

coveralls commented 4 years ago

Coverage Status

Coverage remained the same at 85.313% when pulling 450f9db788850c3db356d1cc9929f55aa530a06a on lapetina9:review-overview-development into 70ded9e77372752355e0298c6b55d6ee06e28d04 on CityOfZion:development.

ixje commented 4 years ago

@ixje, the documentation website directs to the information in the development branch. Should we leave it like this? Or should we change it?

I think the documentation should point to the latest released version, not to the development branch.

lapetina9 commented 4 years ago

Hi Erik, Thanks for your answer. I think I can't change this configuration. I believe this setting is in the admin pannel in ReadTheDocs. I've found this researching for this problem: https://stackoverflow.com/questions/47125293/change-branch-for-latest-version