New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare for first release #375
Conversation
47c8243
to
a63b761
Compare
So, you can hook the repository into zenodo before a release, but you may need to make a tag before you can have zenodo generate a DOI. Should be pretty simple to find out https://guides.github.com/activities/citable-code/ |
* Jan Schlüter (@f0k) | ||
* Søren Kaae Sønderby (@skaae) | ||
|
||
* extra contributors, in chronological order: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @takacsg84 @instagibbs @peterderivaz
Do any of you want your full name in the contributors list here instead of just your github nickname?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add my real name: Gregory Sanders
Before I forget: I've become busy with other stuff. If someone just wants to poach the PreLU implementation go ahead and take it. Don't have time to finish.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the name. (Good idea to attach the diff comment to a line that's not going to change, so it stays visible!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the other two names. They were actually easy to google.
Okay, found it out. The badge URL includes the DOI, so it's not possible to include it in the very first release (i.e., the very first tag). I hoped that the badge might be generated based on the project name. |
* Jon Crall (@erotemic): check for non-positive input shapes | ||
* Hendrik Weideman (@hjweide): set_all_param_values() test, MaxPool2DCCLayer fix | ||
* Kashif Rasul (@kashif): ADAM simplification | ||
* (@peterderivaz): documentation fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work tracking down all of this :p it's nice to have an overview!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work tracking down all of this :p
In future we should probably add them on the go!
LGTM! Too bad about the badge, but we can add it straight after the release so it's not a huge issue I guess. |
It's just that it won't be visible on PyPI then. (Unless we change the README.rst after tagging, but before doing I've set up Zenodo now. It's waiting for a tag. |
Let's just do that - it seems like the only disadvantage then would be that the README at the tag would be slightly different than the README on pypi, right? |
Yes, I think so. By the way, I've also found this release checklist: https://gist.github.com/audreyr/5990987 |
I've merged this to master locally for testing, and the tests still pass, and the documentation still builds.
What strikes me is that |
Seems we need a |
Okay, added a MANIFEST.in that will make the docs and tests and all *.rst and *.txt files in the root directory part of the source distribution. Set
|
@benanne: Shall I go ahead, merge this and create a tag? (Side question: Should the tag contain all of the changelog, i.e., the contributor lists? The tag commit message is used for the release notes on github: https://github.com/audreyr/cookiecutter/releases/tag/1.0.0) |
|
Okay, merged. Will create the tag at 23:00 CEST! I will include the contributor list just for consistency, as I guess we should include whatever the changelog says for future releases. It's not really meaningful for the first release, but for future ones there will be an actual changelog. |
Yay! Well done everyone. :-) |
GitHub dated back the tag by five minutes! (Created it in the web interface. Maybe their servers are a bit behind.) |
Is there anything I need to do to push it to PyPI? |
Yep, I think you're the only one who can, see #74 (comment)! |
Thank you! |
This adds a changelog as suggested in #74 (comment), updates
requirements.txt
to a Theano version supporting cuDNN v3 as suggested in #74 (comment), and changes the version number from0.1.dev
to0.1
.It assumes we're going to tag the release as
v0.1
(that's how numpy and blocks do it, for example), not as0.1
(that's how, hmm... some projects do it like this). I'm fine with either way. @dnouri might have a preference?It would be nice to have a DOI badge in the README of the first release, but I'm not sure if it's possible to add the DOI badge before we tag the release, which we need to do in order to get a DOI. I'll investigate.