Initial Release Notes for 3.15

[math-a3k]

• Add docs/community/3.15-announcement.md
• Update docs/community/release-notes.md

As mentioned in #8614 (comment)

[tomchristie]

@auvipy Wondering if it'd be worth us pushing forward with this - I'd be happy to make the time for us to work together on getting a new release out.

[auvipy]

we can wait until django 4.2a1 release. I didn't mean to release anything yet. was just thinking of reduce backlog for now.

[math-a3k]

@tomchristie @auvipy While I'm on vacation until ~~ March, I will be happy to collaborate on this.

I have updated the release notes to include recent commits and left a base for the announcement which still need polishing - I think.

Please feel free of editing or contacting if you think something is needed, the ETA for Django 4.2 is on April, I'll check this periodically.

[auvipy]

While I'm on vacation until ~~ March, I will be happy to collaborate on this.

I have updated the release notes to include recent commits and left a base for the announcement which still need polishing - I think.

No worries. thanks for what have you done so far. I will prepare some long standing pending PR merge-able in the mean time. like some deprecation and compatibility with django PR.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[math-a3k]

Hi! I updated this branch with the most recent commits and updated the RN with what I deemed most relevant.

[Tenzer]

Django 4.2 has been released now. DRF users would be blocked from upgrading until a new release is out.

[math-a3k]

Hi! I've updated the PR to include the latest commits (up to today). I also put today as a release date in case it's decided to release the current master as 3.15. From https://github.com/encode/django-rest-framework/milestone/78, it seems that there are no issues related to Django 4.2 left, so it seems to me that this can be a release for Django 4.2 compatibility.

What needs to be checked so far would be the RN (docs/community/3.15-announcement.md) (@auvipy @tomchristie)

[auvipy]

@tomchristie I think we can plan for a new release now. let me know if you want me to release it O:)

[tomchristie]

I think we can plan for a new release now.

@auvipy Looking good yup. Let me know once you think we're all ready and we can make sure to work through it together.

[auvipy]

I think we can plan for a new release now.

@auvipy Looking good yup. Let me know once you think we're all ready and we can make sure to work through it together.

I will review everything this week and early next week and I believe we can make it happen in 2-3 weeks if we all can agree upon.

[auvipy]

we are almost near the feature freeze for the v3.15 release. so if you can update the pr, it would be great

[auvipy]

and another update from the commit log would be really great.

[ebk46]

Is this going live any time soon?

[akittas]

Is there anything blocking this? Do you guys need some help?

[auvipy]

@tomchristie lets try to cut a release this week if you are available.

[tomchristie]

@tomchristie lets try to cut a release this week if you are available.

Yep I'm available. What do we need to do from here?

[HansAarneLiblik]

Any developments on this please?

[tomchristie]

Any developments on this please?

...we'll get there.

(There's plenty of other bits been going on, so just taking a little time.)

[intgr]

Guys, I understand it must be tough letting go of a version number as symbolic as 3.14.

If you don't want to ruin it with 3.15, may I suggest to add another pi digit and make it DRF version 3.141

[ebk46]

Any updates on this? This is preventing our team from doing a proper upgrade to Django 4.2.

[ihoru]

Any updates on this? This is preventing our team from doing a proper upgrade to Django 4.2.

Current version (3.14) works just fine with Django 4.2 for us.

[auvipy]

Any updates on this? This is preventing our team from doing a proper upgrade to Django 4.2.

you can easily work with django 4.2.x with current release

[stianjensen]

Is the plan still to try and release 3.15 this year?

[cracly]

Hey folks, a release would be great, trying to get rid of pytz. Thanks for all the work!

[gdvalderrama]

Honestly, we just updated to Django 4.2 with DRF on 3.14
It works, we've had no issues (been on production for several months)
If we eventually get the 3.15 released that would be great though

[tomchristie]

Okay, I'm working through this now.
Here's a first past clean-up... #9210. Eyes on that appreciated.

I'm somewhat concerned about introducing any non-essential changes to REST framework at this point in it's lifespan. The most sensible flow right now would be...

• One new release alongside each new Django release.
• No changes accepted other than essentials to track required Django, Python, and package updates.

Still, we do need to wrap up the existing state of the current main branch into a new release let's try to get that done.

[mjsir911]

Hi! We're interested too in a new release getting out, specifically for #9017 but just in general, it's been a year and a half now since the last release.

Let me know if there's anything we can do to help!

[TGoddessana]

It looks like Django 5.2 is just around the corner, are there any plans to release 3.15 before then?

[tomchristie]

Superseeded by #9210.

We're currently in the process of resolving with various associated regressions.
Expect a 3.15.1 release shortly. (Disappointing, yep, but we're getting on top of it.)