release comments for 0.0.1

[pavoljuhas]

@CJ-Wright - Please remove the tarball aset 0.0.1.tar.gz from
https://github.com/diffpy/diffpy.pdfmorph/releases/tag/0.0.1.
The github-generated archive has the same content, but downloads
with a correct name (diffpy.pdfmorph-0.0.1.tar.gz) and starts with a correct
diffpy.pdfmorph-0.0.1/ prefix directory.

Also please add release tag v0.0.1 and remove tag 0.0.1 to be consistent with changelog.

[CJ-Wright]

The SHAs of the github tarballs are not stable, which is why we use the uploaded tarballs.
I can try to get the name of the package into the tarball name.

I think were planning on doing a 0.1 release in the very near future so I'd rather not have to go though the effort at this point. I will try to remove the v from the changelog so it matches the tags properly.

[sbillinge]

Hi Pavol, just to add a few words here..... CJ is right, we wanted a quick first release tag so we can get this onto conda, then we will lots of cleaning and testing for a proper 0.1.0 release. This release is not really for the general public (though of course it will be visible. So the less cleaning we have to do here, the better....

…

On Fri, Jun 21, 2019 at 3:06 PM Christopher J. Wright < ***@***.***> wrote: The SHAs of the github tarballs are not stable, which is why we use the uploaded tarballs. I can try to get the name of the package into the tarball name. I think were planning on doing a 0.1 release in the very near future so I'd rather not have to go though the effort at this point. I will try to remove the v from the changelog so it matches the tags properly. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABAOWUP3AMCXZAZAZQASX6TP3URDJANCNFSM4H2UC7AQ> .

-- ---- Prof. Simon Billinge Applied Physics & Applied Mathematics Columbia University 500 West 120th Street Room 200 Mudd, MC 4701 New York, NY 10027 Tel: (212)-854-2918 (o) 851-7428 (lab) Condensed Matter Physics and Materials Science Dept. Brookhaven National Laboratory P.O. Box 5000 Upton, NY 11973-5000 (631)-344-5661 email: sb2896 at columbia dot edu home: http://thebillingegroup.com

[pavoljuhas]

The SHAs of the github tarballs are not stable, which is why we use the uploaded tarballs.

Are github tarballs indeed unstable or was it a one-off change, say due to changing tar.umask in their tarball generator?

I can try to get the name of the package into the tarball name.

The easiest would be to download and save the GH-generated tarball.

I think were planning on doing a 0.1 release in the very near future so I'd rather not have to go though the effort at this point. I will try to remove the v from the changelog so it matches the tags properly.

I use the vX.Y.Z tag naming for other diffpy packages, many OSS projects use the v prefix as well.
Can we stick to a uniform naming scheme? Adding a new v0.0.1 tag is pretty easy.

[chloeann95]

This is just a change in our tag names and removing a redundant file when we go to release correct?

[sbillinge]

This is about what we call the release. Mostly in the group we call a release just by the number, so 1.23.4 let's say. But Pavol wants it to conform to the diffpy standard which is the same but with a prepended v, so v1.23.4.

When we release we will use rever and will type rever vX.Y.Z replacing X, Y and Z with the respective numbers.

I suggest that you do a trial release of something with rever. It takes some setting up and getting it going. Maybe talk to Songsheng and see if there is anything that you can release using rever to test your setup.

[chloeann95]

Thanks will do, just wanted to make sure I understood the issue here.