Skip to content
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

Release cycle? #640

Closed
jessechahal opened this issue Jun 20, 2016 · 9 comments
Closed

Release cycle? #640

jessechahal opened this issue Jun 20, 2016 · 9 comments

Comments

@jessechahal
Copy link
Contributor

So I'm just trying to figure out how often releases are done for moto. We want extend moto whenever we come across gaps in some of the functions in boto but we would rather not maintain our own pypi repo with our custom builds. This is especially important since if we starting versioning moto differently we're going to end up with some conflicts. Is it possible to setup travis to auto deploy to the central pypi repo? https://docs.travis-ci.com/user/deployment/pypi seems to suggest it is quite easy to setup.

@spulec
Copy link
Collaborator

spulec commented Jun 20, 2016

Releases are done about once per month and after any major changes have been merged.

Do you have any examples of other projects doing this?

@jessechahal
Copy link
Contributor Author

@esc
Copy link

esc commented Sep 29, 2016

Yeah, this is super easy. For the pybuilder project, we basically build a pre-release for PyPi whenever the travis tests on master are green:

https://pypi.python.org/pypi/pybuilder

You can then install these pre-releases with:

pip install --pre pybuilder

This is really nice, because a) after you fix a bug, you can simply ask the reporter to install with --pre to test and b) some daring people -- like myself -- simply use the --pre releases in production, which means that I will notice immediately if it does break even though travis was green.

@spulec
Copy link
Collaborator

spulec commented Jul 1, 2019

I've added a first version of this to the project with 6fa51ac. Feedback welcome.

@spulec spulec closed this as completed Jul 1, 2019
@yan12125
Copy link
Contributor

yan12125 commented Jul 2, 2019

There is version 1.3.9 on PyPI: https://pypi.org/project/moto/#history, but no 1.3.9 tag in this git repository. Does something go beyond the expectation?

@spulec
Copy link
Collaborator

spulec commented Jul 2, 2019

Yeah, it looks like my script did not work as intended. I didn't intend to release that.

@yan12125
Copy link
Contributor

yan12125 commented Jul 2, 2019 via email

@yan12125
Copy link
Contributor

1.3.11 is on PyPI [1] but there is no 1.3.11 tag. Is it another un-intended release?

[1] https://pypi.org/project/moto/

@spulec
Copy link
Collaborator

spulec commented Jul 16, 2019

Ugh, yes. Sorry. I feel good that everything is fixed now.

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

4 participants