# Reduce package registration waiting period

**URL:** https://discourse.julialang.org/t/reduce-package-registration-waiting-period/40954
**Category:** Meta Discussion
**Created:** [June 7, 2020, 9:45pm UTC](https://discourse.julialang.org/t/reduce-package-registration-waiting-period/40954 "2020-06-07T21:45:03Z")
**Posts on this page:** 1
**Showing post:** 27

<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: [June 8, 2020, 12:35pm UTC](https://discourse.julialang.org/t/reduce-package-registration-waiting-period/40954/27 "2020-06-08T12:35:42Z")

</div>

> [@anon37204545](#):
>
> it does seem long for packages that can be built in a day or two, or even in just a few hours

I am wondering if the reason for this whole discussions is the two packages you [submitted for registration recently](https://discourse.julialang.org/t/transliterate-jl-isurl-jl-useful-tools/40951), with \<50 lines of runtime code each (one has data as code in addition).

As some people point out in the discussion, in the Julia ecosystem packages it is common for packages to be a bit more complex, . This is exactly the kind of feedback that can happen during the 3-day waiting period. Of course, these are just customs, and you are free to ignore them and register your packages as is.

---

_[View the full topic](https://discourse.julialang.org/t/reduce-package-registration-waiting-period/40954)._