# Julia 1.0.2 testing period

**URL:** <https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121>\
**Category:** Announcements\
**Created:** [November 3, 2018, 8:01pm UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121 "2018-11-03T20:01:47Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)\
**Post date:** [November 3, 2018, 8:01pm UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/1 "2018-11-03T20:01:47Z")

</div>

Hello everyone,

We’re pleased to announce that Julia’s `release-1.0` branch now contains the set of commits we’re planning to call v1.0.2. You can view the list of commits added to this release since v1.0.1 [here](https://github.com/JuliaLang/julia/compare/v1.0.1...b196720). As a patch release, this should be strictly non-breaking for existing code and should introduce no new features at all, just bug fixes and a few performance improvements.

We invite users, especially package authors, to test their code using a source build of Julia’s `release-1.0` branch to ensure there are no changes in behavior aside from bugs being fixed. A package evaluation run showed no regressions from v1.0.1, so we should be all set, but it’s always worthwhile to have more testing and assurance, especially for patch releases. If you run into any issues, please be sure to report them [on GitHub](https://github.com/JuliaLang/julia/issues) by submitting an issue.

Assuming all is well, we plan to move forward with a v1.0.2 release after a few days.

Thanks!

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [November 3, 2018, 8:26pm UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/2 "2018-11-03T20:26:00Z")

</div>

I know a few fixes from Pkg.jl were not included in `v"1.0.1"` since it had not synched in the stdlin pipeline. Could the changes in the stdlib repos be updated to the reader for Julia?

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [November 3, 2018, 9:43pm UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/3 "2018-11-03T21:43:02Z")

</div>

Pkg is now directly downloaded from [Release Pkg v1.0.2 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/releases/tag/v1.0.2).

---

<div class="post-metadata">

**Author:** ![Ronis\_BR](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ronis_br/32/50999_2.png) [@Ronis\_BR](https://discourse.julialang.org/u/Ronis_BR)\
**Post date:** [November 6, 2018, 2:51am UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/4 "2018-11-06T02:51:31Z")

</div>

Hi @ararslan,

Is it possible to provide a binary build (something like a alpha/beta version)? It will help a lot to test the new versions, since there are many people who will not want to install everything needed to build julia from source. Furthermore, the build process can take a lot of time if you do not have a good computer.

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [November 8, 2018, 12:25pm UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/5 "2018-11-08T12:25:55Z")

</div>

This is done for `v"x.y.z-RC"` so it might be nice to have it even if it is for a patch update.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [November 8, 2018, 4:18pm UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/6 "2018-11-08T16:18:07Z")

</div>

Yes, as we’ve said before, at the moment we do not have the human resources to make binaries for prereleases of patch versions. If someone wants to volunteer to do that work then we can have them.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [November 9, 2018, 6:37am UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/7 "2018-11-09T06:37:16Z")

</div>

Where is the code that generates the existing (release) binaries?

---

<div class="post-metadata">

**Author:** ![Ronis\_BR](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ronis_br/32/50999_2.png) [@Ronis\_BR](https://discourse.julialang.org/u/Ronis_BR)\
**Post date:** [November 14, 2018, 1:47am UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/8 "2018-11-14T01:47:38Z")

</div>

Hi @StefanKarpinski!

Can you please describe how this can be achieved? What kind of equipment / operational system should we have to create those releases? Maybe I can help with that!

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [November 14, 2018, 3:20am UTC](https://discourse.julialang.org/t/julia-1-0-2-testing-period/17121/9 "2018-11-14T03:20:36Z")

</div>

You can ask for details on the #releases channel on Slack.