Versioning

[jacob-rosenthal]

Track version number in pathml/_version.py. Other places in the code where we need the version number, such as setup.py and docs/source/conf.py, we read the version number from that file. This will make it easier to track consistently. Also add a section in documentation about versioning. Also add pathml.__version__ for users.

[codecov-commenter]

Codecov Report

Merging #236 (d06c80f) into master (607c7eb) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #236      +/-   ##
==========================================
+ Coverage   85.30%   85.31%   +0.01%     
==========================================
  Files          25       26       +1     
  Lines        2538     2540       +2     
==========================================
+ Hits         2165     2167       +2     
  Misses        373      373              

Impacted Files	Coverage Δ
pathml/__init__.py	100.00% <100.00%> (ø)
pathml/_version.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 607c7eb...d06c80f. Read the comment docs.

[ryanccarelli]

@jacobrosenthaldfci Should this be merged to master as version 1.0.4? Then we see whether the automated workflow works on 1.0.4 before merging dev and releasing 2.0.0?

[jacob-rosenthal]

Yes I think that's a great idea, however since we have already merged #231, which is backwards compatibility breaking due to the changes in the h5path format, I don't think we could do that

[ryanccarelli]

#231 is only merged to dev not master

We could merge this pr directly to master along with #235 as 1.0.4. Then merge #231 -> dev and dev -> master as 2.0.0.