# Status of 4.2 release blockers.

**URL:** <https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088>\
**Category:** Pre-Releases\
**Tags:** 4-2\
**Created:** [January 9, 2023, 10:26am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088 "2023-01-09T10:26:52Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![felixxm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/felixxm/32/2479_2.png) [@felixxm](https://forum.djangoproject.com/u/felixxm)\
**Post date:** [January 9, 2023, 10:26am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/1 "2023-01-09T10:26:52Z")

</div>

Hi y’all 👋 ,

Time to kick off the release process for the next major release, Django 4.2! 🎉

The 4.2 feature freeze is scheduled (according to the [roadmap](https://code.djangoproject.com/wiki/Version4.2Roadmap)) for January 16th. I’d like to release the alpha on the same day 🤞 .

4.2 is already full of [new goodies](https://docs.djangoproject.com/en/dev/releases/4.2/) 🪙, but we have two larger patches we want to finish reviewing:

- [Fixed #34110 – Added in-memory file storage](https://github.com/django/django/pull/16262),
- [Fixed #26029 – Added STORAGES setting](https://github.com/django/django/pull/15610).

Many thanks to contributors from all over the world 🗺 💚

Best,  
Mariusz

---

<div class="post-metadata">

**Author:** ![leandrodesouzadev](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/leandrodesouzadev/32/8981_2.png) [@leandrodesouzadev](https://forum.djangoproject.com/u/leandrodesouzadev)\
**Post date:** [January 9, 2023, 2:41pm UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/2 "2023-01-09T14:41:02Z")

</div>

That’s great news!  
With the included support for psycopg3, is there any advantages in going full async?

---

<div class="post-metadata">

**Author:** ![felixxm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/felixxm/32/2479_2.png) [@felixxm](https://forum.djangoproject.com/u/felixxm)\
**Post date:** [January 12, 2023, 9:07am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/3 "2023-01-12T09:07:12Z")

</div>

Not immediately, but `psycopg` v3 provides async connections and cursors so it was necessary in the long run.

---

<div class="post-metadata">

**Author:** ![felixxm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/felixxm/32/2479_2.png) [@felixxm](https://forum.djangoproject.com/u/felixxm)\
**Post date:** [January 17, 2023, 10:14am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/4 "2023-01-17T10:14:34Z")

</div>

Django 4.2a1 is out:

> **[Django 4.2 alpha 1 released](https://www.djangoproject.com/weblog/2023/jan/17/django-42-alpha-1-released/)**
>
> Posted by Mariusz Felisiak on January 17, 2023

---

<div class="post-metadata">

**Author:** ![felixxm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/felixxm/32/2479_2.png) [@felixxm](https://forum.djangoproject.com/u/felixxm)\
**Post date:** [February 20, 2023, 8:54am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/5 "2023-02-20T08:54:12Z")

</div>

Django 4.2b1 is out:

> **[Django 4.2 beta 1 released](https://www.djangoproject.com/weblog/2023/feb/20/django-42-beta-1-released/)**
>
> Posted by Mariusz Felisiak on February 20, 2023

---

<div class="post-metadata">

**Author:** ![buswedg](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/buswedg/32/3229_2.png) [@buswedg](https://forum.djangoproject.com/u/buswedg)\
**Post date:** [March 4, 2023, 5:12am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/6 "2023-03-04T05:12:14Z")

</div>

so where would this put third-party packages like django-storages?

---

<div class="post-metadata">

**Author:** ![adamchainz](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/adamchainz/32/26_2.png) [@adamchainz](https://forum.djangoproject.com/u/adamchainz)\
**Post date:** [March 7, 2023, 4:21pm UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/7 "2023-03-07T16:21:20Z")

</div>

django-storages will still work the same, it’s just the `STORAGES` setting that is a new way of pointing to your storage backends.

---

<div class="post-metadata">

**Author:** ![felixxm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/felixxm/32/2479_2.png) [@felixxm](https://forum.djangoproject.com/u/felixxm)\
**Post date:** [March 20, 2023, 7:37am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/8 "2023-03-20T07:37:16Z")

</div>

Django 4.2rc1 is out:

> **[Django 4.2 release candidate 1 released](https://www.djangoproject.com/weblog/2023/mar/20/django-42-rc1/)**
>
> Posted by Mariusz Felisiak on March 20, 2023

---

<div class="post-metadata">

**Author:** ![pauloxnet](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/pauloxnet/32/11021_2.png) [@pauloxnet](https://forum.djangoproject.com/u/pauloxnet)\
**Post date:** [March 20, 2023, 9:23am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/9 "2023-03-20T09:23:38Z")

</div>

> The release candidate stage marks the string freeze and the call for translators to submit translations.

We can’t find the release notes strings for version 4.2 on Transifex.

---

<div class="post-metadata">

**Author:** ![felixxm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/felixxm/32/2479_2.png) [@felixxm](https://forum.djangoproject.com/u/felixxm)\
**Post date:** [March 31, 2023, 7:49am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/10 "2023-03-31T07:49:28Z")

</div>

> [@pauloxnet](#):
>
> We can’t find the release notes strings for version 4.2 on Transifex.

Documentation translations for 4.2 will be available after the final release, this is the current workflow.

---

<div class="post-metadata">

**Author:** ![pauloxnet](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/pauloxnet/32/11021_2.png) [@pauloxnet](https://forum.djangoproject.com/u/pauloxnet)\
**Post date:** [March 31, 2023, 9:46am UTC](https://forum.djangoproject.com/t/status-of-4-2-release-blockers/18088/11 "2023-03-31T09:46:35Z")

</div>

Thanks for your clarification, based on that I proposed a change in the flow.

> [@Proposal to change Django documentation translation release flow](https://forum.djangoproject.com/t/proposal-to-change-django-documentation-translation-release-flow/19928):
>
> During the release of Django 4.2 I realized that the updated strings for translation were not present in the “django-docs” project on Transifex. This flow does not allow translated documentation to be available on the website the day the new version of Django is released. Those who do not understand English will therefore not be able to read, for example, the release notes of the new version, unlike those who understand English. I propose to update the flow and allow the translation of the ne…
