From 7de88f25ff9f1681a3c545c69554ca419cfabc59 Mon Sep 17 00:00:00 2001
From: Tim O'Donnell <timodonnell@gmail.com>
Date: Fri, 13 Oct 2017 11:23:25 -0400
Subject: [PATCH] update setup.py
---
RELEASING.md | 21 ---------------------
setup.py | 6 +++---
2 files changed, 3 insertions(+), 24 deletions(-)
delete mode 100644 RELEASING.md
diff --git a/RELEASING.md b/RELEASING.md
deleted file mode 100644
index 4e3c8d6a..00000000
--- a/RELEASING.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Releasing MHCflurry
-
-We currently don't have a PyPI release but that will change soon (and these instructions will be updated indicating how to push updates). For now the only "releasing" to deal with is changing the downloadable models and data.
-
-## Changing the downloadable models or data
-
-We publish our downloadable models and data as files associated with a GitHub release. Since we need to refer to the URLs for these files in [downloads.yml](mhcflurry/downloads.yml), which is checked into the repo, updating the models requires a few steps: we have to make a preliminary GitHub release containing the new models and data as GitHub attached files, update the code to point to these files, wait for travis to run, merge the PR, then modify the release's tag to now point to the new master. Here are these steps in more detail:
-
-* Make a new release by going [here](https://github.com/hammerlab/mhcflurry/releases/new). The tag should be the version of MHCflurry you are releasing. Make sure you check "This is a pre-release." It actually doesn't matter what commit the tag is associated with as we will change it later, but you might as well make it point to HEAD of the branch you are working from. Attach your generated downloads to the release.
-
-* Modify [downloads.yml](mhcflurry/downloads.yml) to point to the URLs of your files above. Commit and push your changes to your branch.
-
-* When travis has suceeded and code review is complete, merge your PR to master.
-
-* Now *change* the GitHub release's tag to point to the current latest master. Based on this stackoverflow [answer](http://stackoverflow.com/questions/24849362/change-connected-commit-on-release-github) you can run (from a checkout of the updated master branch):
-
-```
-git tag -f -a 0.0.1
-git push -f --tags
-```
-
diff --git a/setup.py b/setup.py
index c0f624a9..8c9fca16 100644
--- a/setup.py
+++ b/setup.py
@@ -67,8 +67,8 @@ if __name__ == '__main__':
name='mhcflurry',
version=version,
description="MHC Binding Predictor",
- author="Alex Rubinsteyn <alex@hammerlab.org>, Tim O'Donnell <tim@hammerlab.org>",
- author_email="tim@hammerlab.org",
+ author="Tim O'Donnell and Alex Rubinsteyn",
+ author_email="timodonnell@gmail.com",
url="https://github.com/hammerlab/mhcflurry",
license="http://www.apache.org/licenses/LICENSE-2.0.html",
entry_points={
@@ -81,7 +81,7 @@ if __name__ == '__main__':
]
},
classifiers=[
- 'Development Status :: 3 - Alpha',
+ 'Development Status :: 4 - Beta',
'Environment :: Console',
'Operating System :: OS Independent',
'Intended Audience :: Science/Research',
--
GitLab