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
Comments
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? |
4 other projects that I know of are: |
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:
This is really nice, because a) after you fix a bug, you can simply ask the reporter to install with |
I've added a first version of this to the project with 6fa51ac. Feedback welcome. |
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? |
Yeah, it looks like my script did not work as intended. I didn't intend to release that. |
Thanks! I'll skip version 1.3.9 for now.
Steve Pulec <notifications@github.com> 於 2019年7月2日 週二 上午9:53寫道:
… Yeah, it looks like my script did not work as intended. I didn't intend to
release that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#640>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOZCGJWKRJLJ4KBHRS2HG3P5KYJHANCNFSM4CHFGKTA>
.
|
1.3.11 is on PyPI [1] but there is no 1.3.11 tag. Is it another un-intended release? |
Ugh, yes. Sorry. I feel good that everything is fixed now. |
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.
The text was updated successfully, but these errors were encountered: