matplotlib-devel Mailing List for matplotlib

On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tca...@gm...> wrote:
> Hey all,
>
> Github has made it possible to get a DOI for a release (
> https://guides.github.com/activities/citable-code/ ).
>
> I am inclined to do this for 1.4.0. I think doing this is a good
> first step towards being good (leading?) citizens in the reproducible
> science community.
FYI, since I just spent half an hour figuring this out:
To use the Zenodo magic DOI feature you have to:
1) Attach Zenodo to the repository like it says in the tutorial.
2) Create a "release" on github, which is *not* the same as a tag,
even though the github UI claims that they are identical. See all of
these releases that are listed on your github releases page?
 https://github.com/matplotlib/matplotlib/releases
None of them are actually releases in the sense that Zenodo wants.
Here's an example of what it looks like after you've made Zenodo happy:
 https://github.com/pydata/patsy/releases
The trick is to click "draft a new release", and then type in the name
of your existing tag. You can add some release notes if desired, which
will be copied to the archived Zenodo page, which will look like this:
 https://zenodo.org/record/11445
(The text "See release notes: <url>" is what I typed into the Github
release description box.) And then click "Publish release" obviously.
This will convert your existing release tag into an *extra-special*
release tag, which AFAICT works the same as before except that (a) it
gets snazzier graphics in the github UI, and (b) Zenodo will archive
it.
-n
-- 
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org

https://zenodo.org/record/11451#.U_z6ckREvfQ
And yes, I will create an issue for updating the citation page.
Tom
On Tue, Aug 26, 2014 at 5:08 PM, Benjamin Root <ben...@ou...> wrote:
> In case you weren't already thinking of this, we might want to update this
> page:
> http://matplotlib.org/citing.html
>
>
> On Tue, Aug 26, 2014 at 5:01 PM, Thomas Caswell <tca...@gm...> wrote:
>>
>> Thanks! This hasn't been done yet because I was confused by zenodo and
>> hadn't taken the tune to sort this out.
>>
>> Tom
>>
>> On Aug 26, 2014 4:54 PM, "Nathaniel Smith" <nj...@po...> wrote:
>>>
>>> On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tca...@gm...>
>>> wrote:
>>> > Hey all,
>>> >
>>> > Github has made it possible to get a DOI for a release (
>>> > https://guides.github.com/activities/citable-code/ ).
>>> >
>>> > I am inclined to do this for 1.4.0. I think doing this is a good
>>> > first step towards being good (leading?) citizens in the reproducible
>>> > science community.
>>>
>>> FYI, since I just spent half an hour figuring this out:
>>>
>>> To use the Zenodo magic DOI feature you have to:
>>>
>>> 1) Attach Zenodo to the repository like it says in the tutorial.
>>>
>>> 2) Create a "release" on github, which is *not* the same as a tag,
>>> even though the github UI claims that they are identical. See all of
>>> these releases that are listed on your github releases page?
>>> https://github.com/matplotlib/matplotlib/releases
>>> None of them are actually releases in the sense that Zenodo wants.
>>>
>>> Here's an example of what it looks like after you've made Zenodo happy:
>>> https://github.com/pydata/patsy/releases
>>>
>>> The trick is to click "draft a new release", and then type in the name
>>> of your existing tag. You can add some release notes if desired, which
>>> will be copied to the archived Zenodo page, which will look like this:
>>> https://zenodo.org/record/11445
>>> (The text "See release notes: <url>" is what I typed into the Github
>>> release description box.) And then click "Publish release" obviously.
>>> This will convert your existing release tag into an *extra-special*
>>> release tag, which AFAICT works the same as before except that (a) it
>>> gets snazzier graphics in the github UI, and (b) Zenodo will archive
>>> it.
>>>
>>> -n
>>>
>>> --
>>> Nathaniel J. Smith
>>> Postdoctoral researcher - Informatics - University of Edinburgh
>>> http://vorpus.org
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds. Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
-- 
Thomas Caswell
tca...@gm...

In case you weren't already thinking of this, we might want to update this
page:
http://matplotlib.org/citing.html
On Tue, Aug 26, 2014 at 5:01 PM, Thomas Caswell <tca...@gm...> wrote:
> Thanks! This hasn't been done yet because I was confused by zenodo and
> hadn't taken the tune to sort this out.
>
> Tom
> On Aug 26, 2014 4:54 PM, "Nathaniel Smith" <nj...@po...> wrote:
>
>> On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tca...@gm...>
>> wrote:
>> > Hey all,
>> >
>> > Github has made it possible to get a DOI for a release (
>> > https://guides.github.com/activities/citable-code/ ).
>> >
>> > I am inclined to do this for 1.4.0. I think doing this is a good
>> > first step towards being good (leading?) citizens in the reproducible
>> > science community.
>>
>> FYI, since I just spent half an hour figuring this out:
>>
>> To use the Zenodo magic DOI feature you have to:
>>
>> 1) Attach Zenodo to the repository like it says in the tutorial.
>>
>> 2) Create a "release" on github, which is *not* the same as a tag,
>> even though the github UI claims that they are identical. See all of
>> these releases that are listed on your github releases page?
>> https://github.com/matplotlib/matplotlib/releases
>> None of them are actually releases in the sense that Zenodo wants.
>>
>> Here's an example of what it looks like after you've made Zenodo happy:
>> https://github.com/pydata/patsy/releases
>>
>> The trick is to click "draft a new release", and then type in the name
>> of your existing tag. You can add some release notes if desired, which
>> will be copied to the archived Zenodo page, which will look like this:
>> https://zenodo.org/record/11445
>> (The text "See release notes: <url>" is what I typed into the Github
>> release description box.) And then click "Publish release" obviously.
>> This will convert your existing release tag into an *extra-special*
>> release tag, which AFAICT works the same as before except that (a) it
>> gets snazzier graphics in the github UI, and (b) Zenodo will archive
>> it.
>>
>> -n
>>
>> --
>> Nathaniel J. Smith
>> Postdoctoral researcher - Informatics - University of Edinburgh
>> http://vorpus.org
>>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds. Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Thanks! This hasn't been done yet because I was confused by zenodo and
hadn't taken the tune to sort this out.
Tom
On Aug 26, 2014 4:54 PM, "Nathaniel Smith" <nj...@po...> wrote:
> On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tca...@gm...>
> wrote:
> > Hey all,
> >
> > Github has made it possible to get a DOI for a release (
> > https://guides.github.com/activities/citable-code/ ).
> >
> > I am inclined to do this for 1.4.0. I think doing this is a good
> > first step towards being good (leading?) citizens in the reproducible
> > science community.
>
> FYI, since I just spent half an hour figuring this out:
>
> To use the Zenodo magic DOI feature you have to:
>
> 1) Attach Zenodo to the repository like it says in the tutorial.
>
> 2) Create a "release" on github, which is *not* the same as a tag,
> even though the github UI claims that they are identical. See all of
> these releases that are listed on your github releases page?
> https://github.com/matplotlib/matplotlib/releases
> None of them are actually releases in the sense that Zenodo wants.
>
> Here's an example of what it looks like after you've made Zenodo happy:
> https://github.com/pydata/patsy/releases
>
> The trick is to click "draft a new release", and then type in the name
> of your existing tag. You can add some release notes if desired, which
> will be copied to the archived Zenodo page, which will look like this:
> https://zenodo.org/record/11445
> (The text "See release notes: <url>" is what I typed into the Github
> release description box.) And then click "Publish release" obviously.
> This will convert your existing release tag into an *extra-special*
> release tag, which AFAICT works the same as before except that (a) it
> gets snazzier graphics in the github UI, and (b) Zenodo will archive
> it.
>
> -n
>
> --
> Nathaniel J. Smith
> Postdoctoral researcher - Informatics - University of Edinburgh
> http://vorpus.org
>

Hi Thomas!
Can you send out the DOI once you have it?
-Tobias

We are pleased to announce the release of matplotlib 1.4.0!
This release has contributions from ~170 authors
(http://matplotlib.org/users/github_stats.html).
This release contains many bug fixes as will as a number of new
features. For the full list see
http://matplotlib.org/users/whats_new.html#new-in-matplotlib-1-4.
Some highlights are:
 - style module : experimental package to make managing the style of
matplotlib figures easier
 - nbagg : interactive figures in ipython notebooks backed by the AGG renderer
 - full python 3 support (including cairo backends)
 - Qt5 support (for python 3 only)
 - violin plots and 3D quiver plots (projects done for a course at
University of Toronto, Scarborough)
 - new box plot interface (as bxp)
The release can be installed via pip (but requires local compilation)
Tarballs are available at:
 - http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.4.0/matplotlib-1.4.0.tar.gz
 - https://github.com/matplotlib/matplotlib/archive/v1.4.0.tar.gz
 - https://pypi.python.org/packages/source/m/matplotlib/matplotlib-1.4.0.tar.gz
Windows install binaries and wheels are available (thanks to Christoph
Gohlke) at http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.4.0/
.
Mac OSX wheels are available (thanks to Matthew Brett) from
http://wheels.scikit-image.org .
The Matplotlib Team

On 8/25/2014 8:25 PM, Thomas Caswell wrote:
> I have tagged 1.4.0, posted the source tarball to sf, updated pypi,
> updated the docs, and kicked off building the mac wheels.
>
> Holding off on announcing to the rest of the lists until the windows
> binaries get built.
>
> Created a v1.4.0-doc branch on the main repo to put documentation
> updates in. One of the big issues from 1.3.1 was the incorrect
> documentation for the windows install that was wrong for many months,
> hopefully this will give us a way to deal with future situations
> rapidly.
>
> Tom
>
Hi Tom,
I uploaded the Windows installers, wheels, and compiled help file to SF. 
As usual the release version binaries do not include the tests or sample 
data. Built against numpy versions 1.6.2 (Python <= 3.2), 1.7.2 (Python 
3.3) and 1.8.2 (Python 3.4).
Christoph

I have tagged 1.4.0, posted the source tarball to sf, updated pypi,
updated the docs, and kicked off building the mac wheels.
Holding off on announcing to the rest of the lists until the windows
binaries get built.
Created a v1.4.0-doc branch on the main repo to put documentation
updates in. One of the big issues from 1.3.1 was the incorrect
documentation for the windows install that was wrong for many months,
hopefully this will give us a way to deal with future situations
rapidly.
Tom
-- 
Thomas Caswell
tca...@gm...