# Julia 1.5.2 testing period

**URL:** <https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657>\
**Category:** Announcements\
**Tags:** release\
**Created:** [September 15, 2020, 7:21pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657 "2020-09-15T19:21:57Z")\
**Posts on this page:** 12\
**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:** [September 15, 2020, 7:21pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/1 "2020-09-15T19:21:57Z")

</div>

The `release-1.5` branch on the Julia repository now contains the set of commits we’re planning to tag as v1.5.2, the second patch release in the 1.5 series. The list of commits included since v1.5.1 is available [here](https://github.com/JuliaLang/julia/compare/v1.5.1...005352a3625813ef199270d00af9b8c4480d792d). As a patch release, it should be strictly non-breaking for existing code and should introduce no new features at all, just bug fixes and performance enhancements.

We encourage users, especially package authors, to test their code using a source build of the `release-1.5` branch to ensure there are no changes in behavior. (Binaries are not available for prereleases of patch versions at this time.) A package evaluation run showed no regressions from v1.5.1, so we should be good, but extra testing and assurance is always worthwhile. If you run into any issues, please report them on Julia’s [GitHub issue tracker](https://github.com/JuliaLang/julia/issues).

Assuming all is well, we’ll move forward with releasing v1.5.2 in a few days.

---

<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:** [September 15, 2020, 7:53pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/2 "2020-09-15T19:53:39Z")

</div>



---

<div class="post-metadata">

**Author:** ![rveltz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rveltz/32/2707_2.png) [@rveltz](https://discourse.julialang.org/u/rveltz)\
**Post date:** [September 15, 2020, 8:41pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/3 "2020-09-15T20:41:29Z")

</div>

does it contain the way v1.6 print package version issues in color etc? (I love it)

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [September 15, 2020, 8:44pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/4 "2020-09-15T20:44:56Z")

</div>

Nope, that’s a new feature. Patch releases only include bug fixes.

> [@ararslan](#):
>
> As a patch release, it should be strictly non-breaking for existing code and should introduce no new features at all, just bug fixes and performance enhancements.

---

<div class="post-metadata">

**Author:** ![DKad](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dkad/32/203663_2.png) [@DKad](https://discourse.julialang.org/u/DKad)\
**Post date:** [September 15, 2020, 9:06pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/5 "2020-09-15T21:06:59Z")

</div>

I tried to find v1.5.2 but only found v1.6.0 on github. Is there a link to v1.5.2?

---

<div class="post-metadata">

**Author:** ![ImreSamu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/imresamu/32/20677_2.png) [@ImreSamu](https://discourse.julialang.org/u/ImreSamu)\
**Post date:** [September 15, 2020, 10:16pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/6 "2020-09-15T22:16:26Z")

</div>

probably this is the proposed v.1.5.2 [https://github.com/JuliaLang/julia/commits/release-1.5](https://github.com/JuliaLang/julia/commits/release-1.5)  
( cc: @Dkad )

---

<div class="post-metadata">

**Author:** ![jebej](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jebej/32/1784_2.png) [@jebej](https://discourse.julialang.org/u/jebej)\
**Post date:** [September 16, 2020, 2:56pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/7 "2020-09-16T14:56:21Z")

</div>

The version has not been released, you must compile from source.

> [@ararslan](#):
>
> We encourage users, especially package authors, to test their code using a source build of the `release-1.5` branch to ensure there are no changes in behavior. (Binaries are not available for prereleases of patch versions at this time.)

It would be nice to post binaries to make testing more widely available. For Windows users in particular it is tricky to compile julia from source.

---

<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:** [September 16, 2020, 3:08pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/8 "2020-09-16T15:08:51Z")

</div>

Linux: [https://s3.amazonaws.com/julialangnightlies/assert\_pretesting/linux/x64/1.5/julia-b8b7267ef3-linux64.tar.gz](https://s3.amazonaws.com/julialangnightlies/assert_pretesting/linux/x64/1.5/julia-b8b7267ef3-linux64.tar.gz)  
mac: [https://s3.amazonaws.com/julialangnightlies/assert\_pretesting/mac/x64/1.5/julia-b8b7267ef3-mac64.dmg](https://s3.amazonaws.com/julialangnightlies/assert_pretesting/mac/x64/1.5/julia-b8b7267ef3-mac64.dmg)  
windows: [https://s3.amazonaws.com/julialangnightlies/assert\_pretesting/winnt/x64/1.5/julia-b8b7267ef3-win64.exe](https://s3.amazonaws.com/julialangnightlies/assert_pretesting/winnt/x64/1.5/julia-b8b7267ef3-win64.exe)

---

<div class="post-metadata">

**Author:** ![Wikunia](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wikunia/32/2180_2.png) [@Wikunia](https://discourse.julialang.org/u/Wikunia)\
**Post date:** [September 18, 2020, 7:57am UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/9 "2020-09-18T07:57:20Z")

</div>

I’m currently running into a failure in precompiling DataFrames with v1.5.2 as downloaded by the link provided by @kristoffer.carlsson on Linux See: [https://github.com/JuliaData/DataFrames.jl/issues/2437](https://github.com/JuliaData/DataFrames.jl/issues/2437)  
Will open an issue on the Julia repo if this is a problem in Julia itself.

---

<div class="post-metadata">

**Author:** ![bkamins](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bkamins/32/208538_2.png) [@bkamins](https://discourse.julialang.org/u/bkamins)\
**Post date:** [September 18, 2020, 9:51am UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/10 "2020-09-18T09:51:05Z")

</div>

I confirm - on Linux it errors, while on Windows it works.

---

<div class="post-metadata">

**Author:** ![bkamins](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bkamins/32/208538_2.png) [@bkamins](https://discourse.julialang.org/u/bkamins)\
**Post date:** [September 18, 2020, 9:54am UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/11 "2020-09-18T09:54:32Z")

</div>

The problem is not with DataFrames.jl but with CategoricalArrays.jl. CC @nalimilan

---

<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:** [September 18, 2020, 12:44pm UTC](https://discourse.julialang.org/t/julia-1-5-2-testing-period/46657/12 "2020-09-18T12:44:21Z")

</div>

The problem exists in 1.5.1 as well. It’s just that those links I posted has assertions enabled. So it is not a regression but a general 1.5 bug.
