upped version for release to pypi

[edsu]

No description provided.

[edsu]

@dbrunton if you want to merge the version increment I can push it up to PyPI

[dbrunton]

Look right now?

On Fri, Sep 19, 2014 at 3:11 PM, Ed Summers notifications@github.com
wrote:

@dbrunton https://github.com/dbrunton if you want to merge the version
increment I can push it up to PyPI

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

[dbrunton]

Erm, I mean now. Sorry about that. I shouldn't be allowed to touch anything
after 3:00 on a Friday.

On Fri, Sep 19, 2014 at 3:15 PM, David Brunton dbrunton@gmail.com wrote:

Look right now?

On Fri, Sep 19, 2014 at 3:11 PM, Ed Summers notifications@github.com
wrote:

@dbrunton https://github.com/dbrunton if you want to merge the version
increment I can push it up to PyPI

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

[edsu]

Me neither. But it didn't stop me from uploading v1.5.2 to PyPI. Have a good weekend 😄

[dbrunton]

HAHAHAHA, good stuff! You have a good weekend, too :)

On Fri, Sep 19, 2014 at 3:22 PM, Ed Summers notifications@github.com
wrote:

Me neither. But it didn't stop me from uploading v1.5.2 to PyPI. Have a
good weekend [image: 😄]

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

[edsu]

Oh, it might be worth doing a:

git tag v1.5.2 
git push --tags 

[dbrunton]

I used the GitHub UI resulting in this:

https://github.com/LibraryOfCongress/bagit-python/tree/v1.5.2

Does that look right?

On Fri, Sep 19, 2014 at 3:24 PM, Ed Summers notifications@github.com
wrote:

Oh, might be worth doing a:

git tag v1.5.2
git push --tags

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

[edsu]

👍