Skip to content

update the release script #177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
10 tasks done
gdementen opened this issue Mar 29, 2017 · 9 comments
Closed
10 tasks done

update the release script #177

gdementen opened this issue Mar 29, 2017 · 9 comments

Comments

@gdementen
Copy link
Contributor

gdementen commented Mar 29, 2017

It is becoming hard to remember to do everything when doing a release, so we should automate the process as much as possible. Here are a few steps:

  • add new methods/functions in api.rst if not done yet (marked as done because I see no way to automate this)
  • update version (meta.yaml, __init__.py and setup.py)
  • update changelog date
  • git tag release
  • git push
  • build documentation (we can probably use hooks to get that done automatically)
  • publish on pypi
  • update conda-forge feedstock to trigger new packages
  • update larrayenv
  • announce the release (once appveyor finally built the package for Windows :)) on larray-announce and possibly pyannounce or pydata or whatever.
@alixdamman
Copy link
Collaborator

Why did you add a bullet build documentation (we can probably use hooks to get that done automatically) ? The documentation is build automatically on readthedocs, no?

@gdementen
Copy link
Contributor Author

Yes, but it was not at the time I created the issue!

@alixdamman
Copy link
Collaborator

assume #411 is done.

@alixdamman
Copy link
Collaborator

instead of rmtree, use rd /s /q <directory>.

@alixdamman alixdamman removed this from the 0.27 milestone Nov 5, 2017
@gdementen
Copy link
Contributor Author

@alixdamman shouldn't this issue be closed?

@alixdamman
Copy link
Collaborator

Considering #411, we open a new issue or we edit this one?

@gdementen
Copy link
Contributor Author

given #411 is closed, I guess we can close this issue, right?

@gdementen
Copy link
Contributor Author

The release script needs to be updated to use the releaser lib. Do you prefer to keep this issue open for that or to close this issue and open a new one?

@alixdamman
Copy link
Collaborator

I opened a new issue : #537

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants