Release version 2.3 on pypi

[pauloxnet]

I think its time to release a new version with support for Django 3+ and Python 3.6+

---

• Update changelog #315
• Restore an example of a dependent setting to the docs #309
• Fix "reference target not found" warnings in the docs #310
• Add new AUTHORS since 2.2 release #319
• Finalize changelog for 2.3 release #320
• Publish release: https://github.com/jazzband/django-configurations/releases/tag/untagged-6ba2bc9f41d4148913fc
• Get Project Lead to push to PyPI: PyPI Release: django-configurations help#254
• Update docs on RTD

[fronbasal]

Bump

[brianhelba]

We need to update the release notes before this happens, but I agree it's a high priority issue.

[brianhelba]

@pauloxnet Are there any other critical issues that need to be fixed before 2.3? I'd like to get the doc fixes in, just so ReadTheDocs doesn't have problems. All the other current PRs could wait for a 2.4 release (which we can issue as soon as we want, we don't have to wait 2 more years 😄).

Also, we need permission to publish to PyPI. I've applied to be a Project Lead, and I'm happy to help with this and future releases: jazzband/help#253 Alternatively, we need to have one of the existing Project Leads do this, but I'd like something more sustainable so we can issue other releases more frequently on the future.

I'm updating the description of this issue with a checklist.

[brianhelba]

I think we should not include #244 in 2.3, since it's too big of a change to merge at the very last minute.

I think we should wait on #307 too. I don't want to immediately promise support for versions that we've only just started to test.

[pauloxnet]

I think we should not include #244 in 2.3, since it's too big of a change to merge at the very last minute.
I think we should wait on #307 too. I don't want to immediately promise support for versions that we've only just started to test.

I agree in avoiding to merge #244 and #307 before 2.3 release

[pauloxnet]

@brianhelba @auvipy I think we're ready to release the version 2.3, maybe we have only add a date in Changelog and update Authors

[auvipy]

yeah sure

[brianhelba]

@brianhelba @auvipy I think we're ready to release the version 2.3, maybe we have only add a date in Changelog and update Authors

Good point, I forgot about AUTHORS. I will update that now and finalize the changelog.

---

I think we should freeze all other merges until after the release.

---

The good news about needing a Project Lead is that apparently since the Jazzband release process doesn't push directly to PyPI, we should be able to create a GitHub release being normal maintainers. We will still need someone upstream at Jazzband to transfer it to PyPI, but hopefully making the release will get their attention.

[brianhelba]

I've also created a draft release: https://github.com/jazzband/django-configurations/releases/tag/untagged-6ba2bc9f41d4148913fc and updated the task checklist accordingly.

[brianhelba]

Ok, I'm going to publish the release now, since all of the PRs are merged and I haven't heard any other comments (but I have seen PR approvals from both @auvipy and @pauloxnet ). 🎉

[pauloxnet]

Thanks. 🥳

[pauloxnet]

@brianhelba thanks for the 2.3 release, so now we have to wait only for a push on PyPi ?

P.S. please use "Rebase and Merge" instead of "Create a merge commit" when merge a Merge Request

[jezdez]

This is done. Thanks, y'all!