Rel/0.13.0 #2011
Rel/0.13.0 #2011
Conversation
* upstream/master: added migp options
| :Date: |today| | ||
| | ||
| Previous versions: `0.12.0 <http://nipype.readthedocs.io/en/0.12.0/>`_ `0.11.0 <http://nipy.org/nipype/0.11.0>`_ | ||
| Previous versions: `0.12.1 <http://nipype.readthedocs.io/en/0.12.1/>`_ `0.11.0 <http://nipy.org/nipype/0.11.0>`_ |
There was a problem hiding this comment.
This is intentionally dropping 0.12.0 from the list (rather than prepending 0.12.1)?
There was a problem hiding this comment.
yes - this should have been done after the 0.12.1 release but we missed it. and we use version in terms of minor element (11, 12, 13, etc.,.)
right after this release, when we switch back to the dev version this will become 0.13.0
CHANGES Outdated
| Upcoming Release | ||
| ===================== | ||
| 0.13.0 (May 11, 2017) | ||
| ============================ |
There was a problem hiding this comment.
I think the extra =s are stylistically frowned upon.
| Could we hold on for a moment - @jokedurnez is about to add her name to .zenodo.json. |
| @chrisfilo - sure just ping me when it's done. |
| done |
* upstream/master: lets keep Satra the senior Update .zenodo.json
| now i'll wait for everything to pass on master and look at the docs and then tag the release. i also realized that for some reason tagging on github doesn't create an annotated tag. so i'll tag locally and push the tag. |
| Don't forget to copypaste changelog into the release description on github. …On Thu, May 11, 2017 at 6:08 PM, Satrajit Ghosh ***@***.***> wrote: now i'll wait for everything to pass on master and look at the docs and then tag the release. i also realized that for some reason tagging on github doesn't create an annotated tag. so i'll tag locally and push the tag. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2011 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOkp8_s1GmRZKOvw95QGiZxCp2GtDUWks5r47EjgaJpZM4NYswX> . |
| | ||
| You can follow the `Nipype tutorial <https://miykael.github.io/nipype_tutorial/>`_ | ||
| | ||
| or use this docker container: `docker pull nipype/nipype` |
There was a problem hiding this comment.
should we add a tag to the container?
4 participants
here it is. please review this before we merge and tag the release.