Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
> But I can't change those settings, these are not my packages. You set in the yml file, you can do it in a PR. On Friday, August 5, 2016 at 4:00:08 PM UTC-7, David Anthoff wrote: > > > There's a setting on both travis and appveyor where you can mark certain > > entries in the build matrix as allowed failures. So they will run and > you can > > look at the logs, but failing won't cause a red status. This is good for > nightlies > > or when a package doesn't entirely support 32 bit, etc. > > But I can't change those settings, these are not my packages. > > > You should be changing the appveyor files in the same PR to add testing > > against 0.5 anyway. Same on Travis, "release" is going to change meaning > so > > it's better to split entries for 0.4 and 0.5. > > Yep, been doing that. > > > What I'll do right now is replace the 0.5-latest downloads on s3 with > rc1+1. > > That way Travis and Appveyor can have this bug fixed, but we're not > making > > a new tag until more things are backported. > > That is perfect, that will completely solve this problem, thanks! >
RE: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
> There's a setting on both travis and appveyor where you can mark certain > entries in the build matrix as allowed failures. So they will run and you can > look at the logs, but failing won't cause a red status. This is good for > nightlies > or when a package doesn't entirely support 32 bit, etc. But I can't change those settings, these are not my packages. > You should be changing the appveyor files in the same PR to add testing > against 0.5 anyway. Same on Travis, "release" is going to change meaning so > it's better to split entries for 0.4 and 0.5. Yep, been doing that. > What I'll do right now is replace the 0.5-latest downloads on s3 with rc1+1. > That way Travis and Appveyor can have this bug fixed, but we're not making > a new tag until more things are backported. That is perfect, that will completely solve this problem, thanks!
RE: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
There's a setting on both travis and appveyor where you can mark certain entries in the build matrix as allowed failures. So they will run and you can look at the logs, but failing won't cause a red status. This is good for nightlies or when a package doesn't entirely support 32 bit, etc. You should be changing the appveyor files in the same PR to add testing against 0.5 anyway. Same on Travis, "release" is going to change meaning so it's better to split entries for 0.4 and 0.5. What I'll do right now is replace the 0.5-latest downloads on s3 with rc1+1. That way Travis and Appveyor can have this bug fixed, but we're not making a new tag until more things are backported.
RE: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
You mean I could just ignore the appveyor failures? I don’t want to do that, I don’t know these packages and who knows what new bugs I might introduce. Or you mean I could update their appveyor files? Then I need two cycles of PRs per package merged, first my update to appveyor, then once that is done I can submit the PR with the julia 0.5 compat stuff, and then I should really follow up with each of these packages to change the appveyor file back to the right stuff once RC2 is out. Quite frankly, that is too cumbersome for me, I’ll just wait for RC2 for now… From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of Tony Kelman Sent: Friday, August 5, 2016 3:25 PM To: julia-users <julia-users@googlegroups.com> Subject: Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available > I’m not going to change their appveyor to nightly builds Why not? You can make it an allowed failure for now. On Friday, August 5, 2016 at 3:17:29 PM UTC-7, David Anthoff wrote: Well, I was hopping around opening PRs in packages that I don’t maintain and fixing 0.5 compat things in those packages. I’m not going to change their appveyor to nightly builds, so I’ll just stop fixing other packages until RC2 is out. From: julia...@googlegroups.com [mailto: julia...@googlegroups.com] On Behalf Of Tony Kelman Sent: Friday, August 5, 2016 2:56 PM To: julia-users < julia...@googlegroups.com> Subject: Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available Use nightly for now, or change your appveyor script to temporarily download these rc1+1 binaries. There are a lot of things pending for backporting to the release-0.5 branch, and I'd like to test them properly before making another tag. On Friday, August 5, 2016 at 2:26:47 PM UTC-7, David Anthoff wrote: Any chance you could just tag RC2 really soon, before the normal weekly schedule? This <https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549> https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549 being on RC1 essentially breaks all appveyor builds on julia 0.5 right now, and that makes cleaning up packages really difficult. Manual links to RC1+1 binaries don’t end up on the appveyor builds, so that is not really a practical option. My sense is that people would have to put package cleanup on hold until appveyor builds are back in business, which seems really not good. After all the whole point of releasing these RCs that are not candidates for a release is presumably so that package maintainers can get their packages to work on 0.5. Cheers, David From: <mailto:julia...@googlegroups.com> julia...@googlegroups.com [ <mailto:julia...@googlegroups.com> mailto:julia...@googlegroups.com] On Behalf Of Tony Kelman Sent: Friday, August 5, 2016 10:49 AM To: julia-users < <mailto:julia...@googlegroups.com> julia...@googlegroups.com> Subject: Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available rc1+1 on the release-0.5 branch has the bug fixed, and may be more useful to test against: https://s3.amazonaws.com/julianightlies/bin/linux/arm/0.5/julia-0.5.0-acfd04c18b-linuxarm.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x64/0.5/julia-0.5.0-acfd04c18b-linux64.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x86/0.5/julia-0.5.0-acfd04c18b-linux32.tar.gz https://s3.amazonaws.com/julianightlies/bin/osx/x64/0.5/julia-0.5.0-acfd04c18b-osx.dmg https://s3.amazonaws.com/julianightlies/bin/winnt/x64/0.5/julia-0.5.0-acfd04c18b-win64.exe https://s3.amazonaws.com/julianightlies/bin/winnt/x86/0.5/julia-0.5.0-acfd04c18b-win32.exe (these links will stop working in about a month since julianightlies doesn't keep files around forever, but consider this an early preview between rc1 and rc2) On Thursday, August 4, 2016 at 10:51:09 AM UTC-7, Tony Kelman wrote: > always the latest RC, and then the final version? Yes. We don't currently do automated nightly builds from release branches. Any sha from a branch within JuliaLang/julia can easily be built on demand though. On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: Excellent! Going forward, what will I get from <http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe> http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe I assume not nightly builds from the release-0.5 branch, but always the latest RC, and then the final version? Is there a stable link that would get me the nightly builds from release-0.5 on windows? From: <mailto:julia...@googlegroups.com> julia...@googlegroups.com [ <mailto:julia...@googlegroups.com> mailto:julia...@googlegroups.com] On Behalf Of Tony Kelman Sent: Thursday, August 4, 2016 6:53 AM To: julia-users < <mailto:julia...@googlegroups.com> julia...@googlegroups.com> Subject: [
Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
> I’m not going to change their appveyor to nightly builds Why not? You can make it an allowed failure for now. On Friday, August 5, 2016 at 3:17:29 PM UTC-7, David Anthoff wrote: > > Well, I was hopping around opening PRs in packages that I don’t maintain > and fixing 0.5 compat things in those packages. I’m not going to change > their appveyor to nightly builds, so I’ll just stop fixing other packages > until RC2 is out. > > > > *From:* julia...@googlegroups.com [mailto: > julia...@googlegroups.com ] *On Behalf Of *Tony Kelman > *Sent:* Friday, August 5, 2016 2:56 PM > *To:* julia-users <julia...@googlegroups.com > > *Subject:* Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries > available > > > > Use nightly for now, or change your appveyor script to temporarily > download these rc1+1 binaries. There are a lot of things pending for > backporting to the release-0.5 branch, and I'd like to test them properly > before making another tag. > > On Friday, August 5, 2016 at 2:26:47 PM UTC-7, David Anthoff wrote: > > Any chance you could just tag RC2 really soon, before the normal weekly > schedule? This > https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549 > being on RC1 essentially breaks all appveyor builds on julia 0.5 right now, > and that makes cleaning up packages really difficult. > > > > Manual links to RC1+1 binaries don’t end up on the appveyor builds, so > that is not really a practical option. My sense is that people would have > to put package cleanup on hold until appveyor builds are back in business, > which seems really not good. After all the whole point of releasing these > RCs that are not candidates for a release is presumably so that package > maintainers can get their packages to work on 0.5. > > > > Cheers, > > David > > > > > > *From:* julia...@googlegroups.com [mailto:julia...@googlegroups.com] *On > Behalf Of *Tony Kelman > *Sent:* Friday, August 5, 2016 10:49 AM > *To:* julia-users <julia...@googlegroups.com> > *Subject:* Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries > available > > > > rc1+1 on the release-0.5 branch has the bug fixed, and may be more useful > to test against: > > > https://s3.amazonaws.com/julianightlies/bin/linux/arm/0.5/julia-0.5.0-acfd04c18b-linuxarm.tar.gz > > https://s3.amazonaws.com/julianightlies/bin/linux/x64/0.5/julia-0.5.0-acfd04c18b-linux64.tar.gz > > https://s3.amazonaws.com/julianightlies/bin/linux/x86/0.5/julia-0.5.0-acfd04c18b-linux32.tar.gz > > https://s3.amazonaws.com/julianightlies/bin/osx/x64/0.5/julia-0.5.0-acfd04c18b-osx.dmg > > https://s3.amazonaws.com/julianightlies/bin/winnt/x64/0.5/julia-0.5.0-acfd04c18b-win64.exe > > https://s3.amazonaws.com/julianightlies/bin/winnt/x86/0.5/julia-0.5.0-acfd04c18b-win32.exe > > (these links will stop working in about a month since julianightlies > doesn't keep files around forever, but consider this an early preview > between rc1 and rc2) > > > On Thursday, August 4, 2016 at 10:51:09 AM UTC-7, Tony Kelman wrote: > > > always the latest RC, and then the final version? > > Yes. > > We don't currently do automated nightly builds from release branches. Any > sha from a branch within JuliaLang/julia can easily be built on demand > though. > > > On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: > > Excellent! > > > > Going forward, what will I get from > > > > > http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe > > > > I assume not nightly builds from the release-0.5 branch, but always the > latest RC, and then the final version? > > > > Is there a stable link that would get me the nightly builds from > release-0.5 on windows? > > > > *From:* julia...@googlegroups.com [mailto:julia...@googlegroups.com] *On > Behalf Of *Tony Kelman > *Sent:* Thursday, August 4, 2016 6:53 AM > *To:* julia-users <julia...@googlegroups.com> > *Subject:* [julia-users] Re: Announcing 0.5.0-rc0 and binaries available > > > > 0.5.0-rc1 has been tagged and binaries are now available. > > > https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz > > https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg > > https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe > > https://s3.amazonaws.com/julialang/bin/winnt/x86/0
RE: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
Well, I was hopping around opening PRs in packages that I don’t maintain and fixing 0.5 compat things in those packages. I’m not going to change their appveyor to nightly builds, so I’ll just stop fixing other packages until RC2 is out. From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of Tony Kelman Sent: Friday, August 5, 2016 2:56 PM To: julia-users <julia-users@googlegroups.com> Subject: Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available Use nightly for now, or change your appveyor script to temporarily download these rc1+1 binaries. There are a lot of things pending for backporting to the release-0.5 branch, and I'd like to test them properly before making another tag. On Friday, August 5, 2016 at 2:26:47 PM UTC-7, David Anthoff wrote: Any chance you could just tag RC2 really soon, before the normal weekly schedule? This <https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549> https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549 being on RC1 essentially breaks all appveyor builds on julia 0.5 right now, and that makes cleaning up packages really difficult. Manual links to RC1+1 binaries don’t end up on the appveyor builds, so that is not really a practical option. My sense is that people would have to put package cleanup on hold until appveyor builds are back in business, which seems really not good. After all the whole point of releasing these RCs that are not candidates for a release is presumably so that package maintainers can get their packages to work on 0.5. Cheers, David From: julia...@googlegroups.com [mailto: julia...@googlegroups.com] On Behalf Of Tony Kelman Sent: Friday, August 5, 2016 10:49 AM To: julia-users < julia...@googlegroups.com> Subject: Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available rc1+1 on the release-0.5 branch has the bug fixed, and may be more useful to test against: https://s3.amazonaws.com/julianightlies/bin/linux/arm/0.5/julia-0.5.0-acfd04c18b-linuxarm.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x64/0.5/julia-0.5.0-acfd04c18b-linux64.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x86/0.5/julia-0.5.0-acfd04c18b-linux32.tar.gz https://s3.amazonaws.com/julianightlies/bin/osx/x64/0.5/julia-0.5.0-acfd04c18b-osx.dmg https://s3.amazonaws.com/julianightlies/bin/winnt/x64/0.5/julia-0.5.0-acfd04c18b-win64.exe https://s3.amazonaws.com/julianightlies/bin/winnt/x86/0.5/julia-0.5.0-acfd04c18b-win32.exe (these links will stop working in about a month since julianightlies doesn't keep files around forever, but consider this an early preview between rc1 and rc2) On Thursday, August 4, 2016 at 10:51:09 AM UTC-7, Tony Kelman wrote: > always the latest RC, and then the final version? Yes. We don't currently do automated nightly builds from release branches. Any sha from a branch within JuliaLang/julia can easily be built on demand though. On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: Excellent! Going forward, what will I get from <http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe> http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe I assume not nightly builds from the release-0.5 branch, but always the latest RC, and then the final version? Is there a stable link that would get me the nightly builds from release-0.5 on windows? From: <mailto:julia...@googlegroups.com> julia...@googlegroups.com [ <mailto:julia...@googlegroups.com> mailto:julia...@googlegroups.com] On Behalf Of Tony Kelman Sent: Thursday, August 4, 2016 6:53 AM To: julia-users < <mailto:julia...@googlegroups.com> julia...@googlegroups.com> Subject: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available 0.5.0-rc1 has been tagged and binaries are now available. <https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz <https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg <https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe <https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe> https://s3.amazonaws.com/julialang/bin/win
Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
Use nightly for now, or change your appveyor script to temporarily download these rc1+1 binaries. There are a lot of things pending for backporting to the release-0.5 branch, and I'd like to test them properly before making another tag. On Friday, August 5, 2016 at 2:26:47 PM UTC-7, David Anthoff wrote: > > Any chance you could just tag RC2 really soon, before the normal weekly > schedule? This > https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549 > being on RC1 essentially breaks all appveyor builds on julia 0.5 right now, > and that makes cleaning up packages really difficult. > > > > Manual links to RC1+1 binaries don’t end up on the appveyor builds, so > that is not really a practical option. My sense is that people would have > to put package cleanup on hold until appveyor builds are back in business, > which seems really not good. After all the whole point of releasing these > RCs that are not candidates for a release is presumably so that package > maintainers can get their packages to work on 0.5. > > > > Cheers, > > David > > > > > > *From:* julia...@googlegroups.com [mailto: > julia...@googlegroups.com ] *On Behalf Of *Tony Kelman > *Sent:* Friday, August 5, 2016 10:49 AM > *To:* julia-users <julia...@googlegroups.com > > *Subject:* Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries > available > > > > rc1+1 on the release-0.5 branch has the bug fixed, and may be more useful > to test against: > > > https://s3.amazonaws.com/julianightlies/bin/linux/arm/0.5/julia-0.5.0-acfd04c18b-linuxarm.tar.gz > > https://s3.amazonaws.com/julianightlies/bin/linux/x64/0.5/julia-0.5.0-acfd04c18b-linux64.tar.gz > > https://s3.amazonaws.com/julianightlies/bin/linux/x86/0.5/julia-0.5.0-acfd04c18b-linux32.tar.gz > > https://s3.amazonaws.com/julianightlies/bin/osx/x64/0.5/julia-0.5.0-acfd04c18b-osx.dmg > > https://s3.amazonaws.com/julianightlies/bin/winnt/x64/0.5/julia-0.5.0-acfd04c18b-win64.exe > > https://s3.amazonaws.com/julianightlies/bin/winnt/x86/0.5/julia-0.5.0-acfd04c18b-win32.exe > > (these links will stop working in about a month since julianightlies > doesn't keep files around forever, but consider this an early preview > between rc1 and rc2) > > > On Thursday, August 4, 2016 at 10:51:09 AM UTC-7, Tony Kelman wrote: > > > always the latest RC, and then the final version? > > Yes. > > We don't currently do automated nightly builds from release branches. Any > sha from a branch within JuliaLang/julia can easily be built on demand > though. > > > On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: > > Excellent! > > > > Going forward, what will I get from > > > > > http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe > > > > I assume not nightly builds from the release-0.5 branch, but always the > latest RC, and then the final version? > > > > Is there a stable link that would get me the nightly builds from > release-0.5 on windows? > > > > *From:* julia...@googlegroups.com [mailto:julia...@googlegroups.com] *On > Behalf Of *Tony Kelman > *Sent:* Thursday, August 4, 2016 6:53 AM > *To:* julia-users <julia...@googlegroups.com> > *Subject:* [julia-users] Re: Announcing 0.5.0-rc0 and binaries available > > > > 0.5.0-rc1 has been tagged and binaries are now available. > > > https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz > > https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg > > https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe > > https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe > https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256 > https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5 > > (append .asc to the linux .tar.gz links for gpg signatures) > > > There will be a RC2 next week. An especially nasty bug was introduced on > master right before we branched for release-0.5 and I unfortunately missed > it in my testing. I had a PkgEval run going but tagged before it was > finished, in order to get binaries building. I won't be repeating that > mistake next time. > > > On Sunday, July 31, 2016 at 3:27:29 PM UTC-7, Viral Shah wrote: > > Hello everyone, > > > > You may have noticed 0.5.0-rc0 being tagged last week. The binaries are > now all re
RE: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
Any chance you could just tag RC2 really soon, before the normal weekly schedule? This https://github.com/JuliaLang/julia/pull/17774#issuecomment-237552549 being on RC1 essentially breaks all appveyor builds on julia 0.5 right now, and that makes cleaning up packages really difficult. Manual links to RC1+1 binaries don’t end up on the appveyor builds, so that is not really a practical option. My sense is that people would have to put package cleanup on hold until appveyor builds are back in business, which seems really not good. After all the whole point of releasing these RCs that are not candidates for a release is presumably so that package maintainers can get their packages to work on 0.5. Cheers, David From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of Tony Kelman Sent: Friday, August 5, 2016 10:49 AM To: julia-users <julia-users@googlegroups.com> Subject: Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available rc1+1 on the release-0.5 branch has the bug fixed, and may be more useful to test against: https://s3.amazonaws.com/julianightlies/bin/linux/arm/0.5/julia-0.5.0-acfd04c18b-linuxarm.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x64/0.5/julia-0.5.0-acfd04c18b-linux64.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x86/0.5/julia-0.5.0-acfd04c18b-linux32.tar.gz https://s3.amazonaws.com/julianightlies/bin/osx/x64/0.5/julia-0.5.0-acfd04c18b-osx.dmg https://s3.amazonaws.com/julianightlies/bin/winnt/x64/0.5/julia-0.5.0-acfd04c18b-win64.exe https://s3.amazonaws.com/julianightlies/bin/winnt/x86/0.5/julia-0.5.0-acfd04c18b-win32.exe (these links will stop working in about a month since julianightlies doesn't keep files around forever, but consider this an early preview between rc1 and rc2) On Thursday, August 4, 2016 at 10:51:09 AM UTC-7, Tony Kelman wrote: > always the latest RC, and then the final version? Yes. We don't currently do automated nightly builds from release branches. Any sha from a branch within JuliaLang/julia can easily be built on demand though. On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: Excellent! Going forward, what will I get from http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe I assume not nightly builds from the release-0.5 branch, but always the latest RC, and then the final version? Is there a stable link that would get me the nightly builds from release-0.5 on windows? From: julia...@googlegroups.com <mailto:julia...@googlegroups.com> [mailto:julia...@googlegroups.com] On Behalf Of Tony Kelman Sent: Thursday, August 4, 2016 6:53 AM To: julia-users <julia...@googlegroups.com <mailto:julia...@googlegroups.com> > Subject: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available 0.5.0-rc1 has been tagged and binaries are now available. <https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz <https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg <https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe <https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe> https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe <https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256 <https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5 (append .asc to the linux .tar.gz links for gpg signatures) There will be a RC2 next week. An especially nasty bug was introduced on master right before we branched for release-0.5 and I unfortunately missed it in my testing. I had a PkgEval run going but tagged before it was finished, in order to get binaries building. I won't be repeating that mistake next time. On Sunday, July 31, 2016 at 3:27:29 PM UTC-7, Viral Shah wrote: Hello everyone, You may have noticed 0.5.0-rc0 being tagged last week. The binaries are now all ready and available for testing. This is a good point for package developers to make their packages ready for 0.5, and for users to test their codes o
Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
rc1+1 on the release-0.5 branch has the bug fixed, and may be more useful to test against: https://s3.amazonaws.com/julianightlies/bin/linux/arm/0.5/julia-0.5.0-acfd04c18b-linuxarm.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x64/0.5/julia-0.5.0-acfd04c18b-linux64.tar.gz https://s3.amazonaws.com/julianightlies/bin/linux/x86/0.5/julia-0.5.0-acfd04c18b-linux32.tar.gz https://s3.amazonaws.com/julianightlies/bin/osx/x64/0.5/julia-0.5.0-acfd04c18b-osx.dmg https://s3.amazonaws.com/julianightlies/bin/winnt/x64/0.5/julia-0.5.0-acfd04c18b-win64.exe https://s3.amazonaws.com/julianightlies/bin/winnt/x86/0.5/julia-0.5.0-acfd04c18b-win32.exe (these links will stop working in about a month since julianightlies doesn't keep files around forever, but consider this an early preview between rc1 and rc2) On Thursday, August 4, 2016 at 10:51:09 AM UTC-7, Tony Kelman wrote: > > > always the latest RC, and then the final version? > > Yes. > > We don't currently do automated nightly builds from release branches. Any > sha from a branch within JuliaLang/julia can easily be built on demand > though. > > > On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: >> >> Excellent! >> >> >> >> Going forward, what will I get from >> >> >> >> >> http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe >> >> >> >> I assume not nightly builds from the release-0.5 branch, but always the >> latest RC, and then the final version? >> >> >> >> Is there a stable link that would get me the nightly builds from >> release-0.5 on windows? >> >> >> >> *From:* julia...@googlegroups.com [mailto:julia...@googlegroups.com] *On >> Behalf Of *Tony Kelman >> *Sent:* Thursday, August 4, 2016 6:53 AM >> *To:* julia-users <julia...@googlegroups.com> >> *Subject:* [julia-users] Re: Announcing 0.5.0-rc0 and binaries available >> >> >> >> 0.5.0-rc1 has been tagged and binaries are now available. >> >> >> https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz >> >> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz >> >> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz >> >> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg >> >> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe >> >> https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe >> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256 >> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5 >> >> (append .asc to the linux .tar.gz links for gpg signatures) >> >> >> There will be a RC2 next week. An especially nasty bug was introduced on >> master right before we branched for release-0.5 and I unfortunately missed >> it in my testing. I had a PkgEval run going but tagged before it was >> finished, in order to get binaries building. I won't be repeating that >> mistake next time. >> >> >> On Sunday, July 31, 2016 at 3:27:29 PM UTC-7, Viral Shah wrote: >> >> Hello everyone, >> >> >> >> You may have noticed 0.5.0-rc0 being tagged last week. The binaries are >> now all ready and available for testing. This is a good point for package >> developers to make their packages ready for 0.5, and for users to test >> their codes on the new release. >> >> >> >> >> https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc0-linux-arm.tar.gz >> >> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc0-linux-x86_64.tar.gz >> >> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc0-linux-i686.tar.gz >> >> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc0-osx10.7+.dmg >> >> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc0-win64.exe >> >> https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc0-win32.exe >> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.sha256 >> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.md5 >> >> >> >> We expect to have a new rc roughly every week until all the dust settles >> and 0.5.0 is finally released. Follow the progress at: >> >> >> >> https://github.com/JuliaLang/julia/issues/17418 >> >> >> >> -viral >> >> >> >>
Re: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
> always the latest RC, and then the final version? Yes. We don't currently do automated nightly builds from release branches. Any sha from a branch within JuliaLang/julia can easily be built on demand though. On Thursday, August 4, 2016 at 10:02:54 AM UTC-7, David Anthoff wrote: > > Excellent! > > > > Going forward, what will I get from > > > > > http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe > > > > I assume not nightly builds from the release-0.5 branch, but always the > latest RC, and then the final version? > > > > Is there a stable link that would get me the nightly builds from > release-0.5 on windows? > > > > *From:* julia...@googlegroups.com [mailto: > julia...@googlegroups.com ] *On Behalf Of *Tony Kelman > *Sent:* Thursday, August 4, 2016 6:53 AM > *To:* julia-users <julia...@googlegroups.com > > *Subject:* [julia-users] Re: Announcing 0.5.0-rc0 and binaries available > > > > 0.5.0-rc1 has been tagged and binaries are now available. > > > https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz > > https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg > > https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe > > https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe > https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256 > https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5 > > (append .asc to the linux .tar.gz links for gpg signatures) > > > There will be a RC2 next week. An especially nasty bug was introduced on > master right before we branched for release-0.5 and I unfortunately missed > it in my testing. I had a PkgEval run going but tagged before it was > finished, in order to get binaries building. I won't be repeating that > mistake next time. > > > On Sunday, July 31, 2016 at 3:27:29 PM UTC-7, Viral Shah wrote: > > Hello everyone, > > > > You may have noticed 0.5.0-rc0 being tagged last week. The binaries are > now all ready and available for testing. This is a good point for package > developers to make their packages ready for 0.5, and for users to test > their codes on the new release. > > > > > https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc0-linux-arm.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc0-linux-x86_64.tar.gz > > https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc0-linux-i686.tar.gz > > https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc0-osx10.7+.dmg > > https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc0-win64.exe > > https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc0-win32.exe > https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.sha256 > https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.md5 > > > > We expect to have a new rc roughly every week until all the dust settles > and 0.5.0 is finally released. Follow the progress at: > > > > https://github.com/JuliaLang/julia/issues/17418 > > > > -viral > > > >
RE: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available
Excellent! Going forward, what will I get from http://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5-latest-win64.exe I assume not nightly builds from the release-0.5 branch, but always the latest RC, and then the final version? Is there a stable link that would get me the nightly builds from release-0.5 on windows? From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of Tony Kelman Sent: Thursday, August 4, 2016 6:53 AM To: julia-users <julia-users@googlegroups.com> Subject: [julia-users] Re: Announcing 0.5.0-rc0 and binaries available 0.5.0-rc1 has been tagged and binaries are now available. <https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc1-linux-arm.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc1-linux-x86_64.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc1-linux-i686.tar.gz <https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc1-osx10.7+.dmg <https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc1-win64.exe <https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe> https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc1-win32.exe <https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.sha256 <https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc1.md5 (append .asc to the linux .tar.gz links for gpg signatures) There will be a RC2 next week. An especially nasty bug was introduced on master right before we branched for release-0.5 and I unfortunately missed it in my testing. I had a PkgEval run going but tagged before it was finished, in order to get binaries building. I won't be repeating that mistake next time. On Sunday, July 31, 2016 at 3:27:29 PM UTC-7, Viral Shah wrote: Hello everyone, You may have noticed 0.5.0-rc0 being tagged last week. The binaries are now all ready and available for testing. This is a good point for package developers to make their packages ready for 0.5, and for users to test their codes on the new release. <https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc0-linux-arm.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/arm/0.5/julia-0.5.0-rc0-linux-arm.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc0-linux-x86_64.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc0-linux-x86_64.tar.gz <https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc0-linux-i686.tar.gz> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc0-linux-i686.tar.gz <https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc0-osx10.7+.dmg> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc0-osx10.7+.dmg <https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc0-win64.exe> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc0-win64.exe <https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc0-win32.exe> https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc0-win32.exe <https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.sha256> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.sha256 <https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.md5> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc0.md5 We expect to have a new rc roughly every week until all the dust settles and 0.5.0 is finally released. Follow the progress at: https://github.com/JuliaLang/julia/issues/17418 -viral
