Document release process #2539
Document release process #2539
Conversation
There was a problem hiding this comment.
Looks good. It might be more informative to generate a changelog based on pull requests (with labels) since they would have more information about new features, vs bug fix etc.
(Jarrod writing) I started looking into this a bit and it will require a little more thought. The current script doesn't work correctly because PRs haven't been merged consistently. So Git doesn't have all the information about what happened in an easy to parse way. I will look into using the GitHub API to get the PR information. It's been a bit since I worked with the GitHub API so I am going to need to figure out whether there are any nice tools or whether I will need to write something from scratch.
In the meantime, I am going to merge this PR since I would like to at least have the release process documented in master (and since I moved and added some files). I will look into options to replace/improve contribs.py and create a separate PR just for that issue. I will also look into why git isn't able to find all the merged PRs and whether we can do something easy to make sure it can going forward. --Jarrod
| - big items ... | ||
|
|
||
| There is a `migration guide for people moving from 1.X to 2.0 | ||
| <http://networkx.readthedocs.org/en/latest/release/migration_guide_from_1.x_to_2.0.html>`_. |
There was a problem hiding this comment.
We need to update this doc. This page was written when G.nodes(), G.edges(), G.degree(), .... were changed to return iterators and now these functions return views.
There was a problem hiding this comment.
@MridulS Would you be willing to create a PR to update:
doc/release/migration_guide_from_1.x_to_2.0.rst
doc/release/release_dev.rst
with this and any other changes, which should be noted?
Am I missing anything obvious? We can fine-tune this as we do the 2.0 release.
(I don't mention making a 2.0 branch as I don't think it is necessary. Particularly, if we are releasing 2.1 soon after the 2.0 release.)