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

Drop Travis #6500

Closed
phadej opened this issue Jan 22, 2020 · 2 comments
Closed

Drop Travis #6500

phadej opened this issue Jan 22, 2020 · 2 comments

Comments

@phadej
Copy link
Collaborator

phadej commented Jan 22, 2020

I have set up the GitHub actions:

  • They worked well for the past month
  • (Recently I added also windows jobs, but let's have appveyor still for time being)
  • Let's also run Travis on 3.2 branch

So now Travis is not needed anymore, but I don't want to pull the trigger without larger acknowledgment. Please comment @23Skidoo, @hvr, @ezyang

@ezyang
Copy link
Contributor

ezyang commented Jan 29, 2020

Go for it. We can get rid of the crazy sake-bot nonsense too once we do this, right?

@phadej
Copy link
Collaborator Author

phadej commented Jan 29, 2020

@ezyang, I'd keep travis setup in 3.2 branch for at least until Summer 2020, just in case.

@phadej phadej closed this as completed in 5f0d1b3 Mar 11, 2020
phadej added a commit that referenced this issue Mar 11, 2020
Drop Travis for master. Resolves #6500.
@phadej phadej added this to the 3.4.0.0-rc1 milestone Jul 13, 2020
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