Skip to content
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

Preparing for Elephant release 0.4.0 #100

Merged
merged 3 commits into from
Mar 22, 2017

Conversation

alperyeg
Copy link
Contributor

For the upcoming neo 0.5.0 release I prepared in parallel the next release for Elephant and adjusted the versions, docs etc. Let me know if something is missing.

@alperyeg alperyeg added the build Travis, libraries, package versioning label Mar 20, 2017
doc/install.rst Outdated
* neo_ == 0.4.0

.. note:: at the time of writing Neo 0.4.0 has not been released. You should therefore use `this snapshot`_.
* neo_ == 0.5.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest making this >=, so when we release Neo 0.5.1, etc., we don't need to change this.


API changes
===========
* Interoperability between Neo 0.5.0beta1 and Elephant
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove "beta1"

@alperyeg alperyeg added this to the Elephant release 0.4.0 milestone Mar 20, 2017
@@ -1,7 +1,6 @@
# Requirements for building documentation
numpy>=1.8.2
quantities>=0.10.1
-e git+https://github.com/NeuralEnsemble/python-neo.git@snapshot-20150821#egg=neo-snapshot-20150821
# note that we use a mock scipy
neo>=0.4.1
Copy link
Member

@apdavison apdavison Mar 20, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

>=0.5.0

@coveralls
Copy link
Collaborator

coveralls commented Mar 20, 2017

Coverage Status

Coverage remained the same at 90.892% when pulling 8e34591 on alperyeg:feature/release_0.4.0 into eec0f3e on NeuralEnsemble:master.

@alperyeg
Copy link
Contributor Author

@apdavison thanks for the quick reply and corrections!

@coveralls
Copy link
Collaborator

Coverage Status

Coverage remained the same at 90.892% when pulling c284b7f on alperyeg:feature/release_0.4.0 into eec0f3e on NeuralEnsemble:master.

3 similar comments
@coveralls
Copy link
Collaborator

Coverage Status

Coverage remained the same at 90.892% when pulling c284b7f on alperyeg:feature/release_0.4.0 into eec0f3e on NeuralEnsemble:master.

@coveralls
Copy link
Collaborator

Coverage Status

Coverage remained the same at 90.892% when pulling c284b7f on alperyeg:feature/release_0.4.0 into eec0f3e on NeuralEnsemble:master.

@coveralls
Copy link
Collaborator

Coverage Status

Coverage remained the same at 90.892% when pulling c284b7f on alperyeg:feature/release_0.4.0 into eec0f3e on NeuralEnsemble:master.

@coveralls
Copy link
Collaborator

Coverage Status

Coverage decreased (-22.9%) to 67.992% when pulling 9e40038 on alperyeg:feature/release_0.4.0 into eec0f3e on NeuralEnsemble:master.

@mdenker mdenker merged commit c137fb5 into NeuralEnsemble:master Mar 22, 2017
@alperyeg alperyeg deleted the feature/release_0.4.0 branch November 24, 2017 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Travis, libraries, package versioning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants