# Julia 1.2 feature freeze April 4th

**URL:** <https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478>\
**Category:** Internals & Design\
**Tags:** announcement, releases\
**Created:** [March 28, 2019, 7:47pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478 "2019-03-28T19:47:04Z")\
**Posts on this page:** 19\
**Page:** 1

<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:** [March 28, 2019, 7:47pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/1 "2019-03-28T19:47:04Z")

</div>

Heads up: this is to let people know that if they have any PRs that they really want to get into Julia 1.2, the feature freeze for the 1.2 release will be one week from today, on Thursday, April 4th. If you want something to be in this release, now is the time to get it done.

---

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [April 3, 2019, 4:24pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/2 "2019-04-03T16:24:21Z")

</div>

CI has been broken for a while now, which makes it pretty hard to get any PRs in — nothing has all passing tests. Have you considered delaying the feature freeze until after CI gets fixed?

---

<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:** [April 3, 2019, 6:50pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/3 "2019-04-03T18:50:21Z")

</div>

@staticfloat: can you clarify the CI status? I.e. what we’re expecting to pass and not to pass now and what all the different test names mean?

---

<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:** [April 3, 2019, 10:49pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/4 "2019-04-03T22:49:47Z")

</div>

Will this release include partr multithreading?

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 3, 2019, 10:54pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/5 "2019-04-03T22:54:46Z")

</div>

I’d like to add `\star` as a unary operation, is that possible for v1.2?

> [@★ is not an operator](https://discourse.julialang.org/t/is-not-an-operator/20221/6):
>
> The ★ operator is actually a unary operator in mathematics, and not a binary infix operator This is a method which I intend to implement for [Grassmann.jl](https://github.com/chakravala/Grassmann.jl)

---

<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:** [April 3, 2019, 10:59pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/6 "2019-04-03T22:59:09Z")

</div>

Not at this point, no. You’d have to convince people that it’s a good idea and then implement it, get it reviewed and merged… all by tomorrow.

---

<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:** [April 3, 2019, 11:00pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/7 "2019-04-03T23:00:25Z")

</div>

Much of it, yes but not the full task-based API. @jeff.bezanson can elaborate with more details.

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 3, 2019, 11:01pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/8 "2019-04-03T23:01:11Z")

</div>

I believe that @stevengj would approve of it

> [@★ is not an operator](https://discourse.julialang.org/t/is-not-an-operator/20221/17):
>
> ★ is [U+2605](https://www.fileformat.info/info/unicode/char/2605/index.htm), “black star”, in Unicode [category So (Symbol, other)](https://www.fileformat.info/info/unicode/category/So/index.htm). For the most part (with the exception of some [arrows](https://en.wikipedia.org/wiki/Arrow_(symbol)#Arrows_in_Unicode)), Julia only parses a subset of [category Sm (Symbol, math)](https://www.fileformat.info/info/unicode/category/Sm/index.htm) as infix operators. In particular, you should look at [U+22C6 (“star operator”)](https://www.fileformat.info/info/unicode/char/22c6/index.htm), typed by tab-completing \star in the REPL, which is in category Sm and is parsed as an infix operator: julia\> ⋆(x,y) = 2x+y ⋆ (generic function with 1 method) julia\> 3 ⋆ 4 10 (Unfortunately, in many fonts, ⋆ is shown rather small.)

---

<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:** [April 3, 2019, 11:02pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/9 "2019-04-03T23:02:31Z")

</div>

The feature freeze is in a few hours at this point, it will have to wait until the next release.

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 3, 2019, 11:13pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/10 "2019-04-03T23:13:20Z")

</div>

Alright, I created the [pull-request](https://github.com/JuliaLang/julia/pull/31604) so that it can be reviewed eventually (hopefully in a few hours).

---

<div class="post-metadata">

**Author:** ![staticfloat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/staticfloat/32/34_2.png) [@staticfloat](https://discourse.julialang.org/u/staticfloat)\
**Post date:** [April 3, 2019, 11:37pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/11 "2019-04-03T23:37:24Z")

</div>

CI should not be broken, with the exception of Linux Travis, which will be fixed once [Fix Travis, which has problems with BB by staticfloat · Pull Request #31605 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/pull/31605) is merged. Everything else (Appveyor, all the buildbots, etc…) should not be broken.

See [this discourse topic](https://discourse.julialang.org/t/upgrading-julialang-julia-buildbot-ci/22078) for more information on CI status.

---

<div class="post-metadata">

**Author:** ![jeff.bezanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeff.bezanson/32/48_2.png) [@jeff.bezanson](https://discourse.julialang.org/u/jeff.bezanson)\
**Post date:** [April 4, 2019, 3:31pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/12 "2019-04-04T15:31:13Z")

</div>

We have done a lot of the internal work on the new threading API but it’s not ready to be exposed yet. The main visible change is that a few more things (task switches and some I/O) work inside `@threads` loops. But I have high hopes that the finishing touches to make the new system fully work will be complete soon.

---

<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:** [April 4, 2019, 3:38pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/13 "2019-04-04T15:38:22Z")

</div>

I have already a PR opened with the `sincosd` function ([Add sincosd function by ronisbr · Pull Request #30134 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/pull/30134)). Should I do something else?

---

<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:** [April 4, 2019, 3:43pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/14 "2019-04-04T15:43:01Z")

</div>

I see, thanks.

Will nested `@threads` loops work properly (depth first)? Or would that require a new API?

---

<div class="post-metadata">

**Author:** ![jeff.bezanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeff.bezanson/32/48_2.png) [@jeff.bezanson](https://discourse.julialang.org/u/jeff.bezanson)\
**Post date:** [April 4, 2019, 4:07pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/15 "2019-04-04T16:07:41Z")

</div>

Not yet; `@threads` just does what it did before (static schedule). In the near future though we should discuss whether `@threads` should switch to depth-first scheduling, or if that should require a different invocation.

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 12, 2019, 2:43pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/16 "2019-04-12T14:43:15Z")

</div>

when will v1.2 be released or frozen? it looks like this hasn’t happened yet

no rush, just wondering what the status of v1.2 release is

---

<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:** [April 12, 2019, 3:35pm UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/17 "2019-04-12T15:35:43Z")

</div>

We’ve branched: [https://github.com/JuliaLang/julia/tree/release-1.2](https://github.com/JuliaLang/julia/tree/release-1.2)

So now we go through the iterative process of release candidates, package evaluation, and backports to that branch until we get an RC we like. I think there are some backports already accrued ([https://github.com/JuliaLang/julia/issues?utf8=✓&amp;q=label%3A"backport+1.2"+is%3Amerged](https://github.com/JuliaLang/julia/issues?utf8=%E2%9C%93&amp;q=label%3A%22backport+1.2%22+is%3Amerged)) that may precede the first RC.

---

<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:** [April 17, 2019, 8:33am UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/18 "2019-04-17T08:33:15Z")

</div>

Workflow clarifying question: if I just want to make PRs for docs fixes, that could ideally end up in 1.2, it is best to do that against `master`, correct? Then the Julia team can decide to backport them to 1.2 or not.

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [April 17, 2019, 8:49am UTC](https://discourse.julialang.org/t/julia-1-2-feature-freeze-april-4th/22478/19 "2019-04-17T08:49:34Z")

</div>

Yes, stuff always go to master first.