Re: [racket-dev] Re: Continuous Integration update and future

2019-11-18 Thread Sam Tobin-Hochstadt
I think there are a few issues worth separating here: 1. snapshot.racket-lang.org is not a download site, but a page with two links. We could fix this by having some redirects/URL rewrites, perhaps from download.racket-lang.org. 2. when one of the snapshot builds fails, there's no notice/somet

Re: [racket-dev] Re: Continuous Integration update and future

2019-11-18 Thread 'John Clements' via Racket Developers
This makes sense to me, but it would be easy to choose the wrong path protocol. Things are definitely interesting around source builds—what do I put for {platform} there? … and of course CS, which is an alternative now but should soon become the default. Also, there are things like “.tgz” bundli

Re: [racket-dev] Re: Continuous Integration update and future

2019-11-18 Thread Philip McGrath
While it's about CI of Racket programs rather than of Racket itself, I wanted to point to a recent discussion on Greg Hendershott's "travis-racket" repository: https://github.com/greghendershott/travis-racket/issues/37 I think it's a very important piece of tooling for the Racket environment, and,

Re: [racket-dev] Re: Continuous Integration update and future

2019-11-18 Thread Sam Tobin-Hochstadt
This sounds great. I see also that Bogdan has developed an action for downloading Racket. Let's continue this work by organizing in the #ci channel on Slack, which I've just created. Anyone else who's interested should join that channel, and we'll work out next steps there. Sam On Sat, Nov 16,

[racket-dev] Completing Racket's re-licensing process

2019-11-18 Thread Sam Tobin-Hochstadt
With the upcoming Racket 7.5 release, almost all of Racket, including the core Racket CS binary, the standard library, and the packages provided with the main distribution, are available under a permissive license, either the Apache 2.0 License or the MIT License. You can read the details of the ne