# Julia's Release Process

**URL:** https://discourse.julialang.org/t/julias-release-process/28122
**Category:** Internals & Design
**Created:** [August 28, 2019, 4:58pm UTC](https://discourse.julialang.org/t/julias-release-process/28122 "2019-08-28T16:58:10Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)
#### Post date: [August 29, 2019, 3:06am UTC](https://discourse.julialang.org/t/julias-release-process/28122/8 "2019-08-29T03:06:12Z")

</div>

Somewhat tangential, but it’d be nice if there is a detailed write up like this for what it means to be a “public API.” I hope I don’t sound nitpicky, but without clear public API, a software is not really SemVer compliant. In particular, I think there are things that should be clearly documented that they are _not_ stable API (output (but not the calling convention) of `show`, type parameters of public `strct`s, etc.). I know Julia has `minor change` as a solution for something like this (and clearly explained in the blog post) but I think discussion in GitHub PRs and issues would be greatly simplified if it does not involve running PkgEval.

---

_[View the full topic](https://discourse.julialang.org/t/julias-release-process/28122)._