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

https://leanpub.com/forging-python/read#leanpub-auto-debugging #3

Closed
venkatveeramanidaasan opened this issue May 7, 2016 · 3 comments

Comments

@venkatveeramanidaasan
Copy link
Contributor

venkatveeramanidaasan commented May 7, 2016

"Graybeard: Yup. Note that there are deploys and there are deploys. Most of them will be a non issue, but some of them will give you a headache."

there are deploys and there are deploys

intentional?

@venkatveeramanidaasan
Copy link
Contributor Author

Graybeard: Also make you you can do a rollback as well. If a release goes back you need to be able to quickly get back. Blue-Green and rolling releases help with this.

back to bad or down?

@tebeka
Copy link
Owner

tebeka commented May 8, 2016

there are deploys and there are deploys

intentional?
Yes. Maybe the wrong idiom/phrasing. I'm saying that not all releases are the same, some are easy, some are difficult.

@tebeka
Copy link
Owner

tebeka commented May 8, 2016

back to bad or down?
typo, fixed. Thanks.

@tebeka tebeka closed this as completed May 8, 2016
tebeka added a commit that referenced this issue May 8, 2016
tebeka pushed a commit that referenced this issue May 21, 2017
…n-patch-2

Core Python speed improvement timeline
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants