Suggested release plan... · encode/django-rest-framework · Discussion #9516 (original) (raw)

You must be logged in to vote

As Python 3.13 is just around the corner, should DRF wait for it to release 3.16?

I think support could be added in 3.16.1 (assuming no major changes), as Django sometimes add support to earlier versions, when the effort is acceptable.

EDIT: addressed in #9527

You must be logged in to vote

0 replies

What is going to be the branching strategy for 3.15.3? I see 2 options:

  1. Branch off 3.15.2 as e.g. stable/3.15.x (same as Django) to cherry pick the changes from master
  2. Release it directly from master

There are a few changes in master that may be better of saving for 3.16, and reinstating older Python/Django versions (IMO) might be easier off master: no need to remove them again. Thoughts? A third option I missed?

You must be logged in to vote

1 reply

@tomchristie

To date we've just released everything from master.
Right now I'd suggest we don't make any changes there.

(Also. master Ugh. Let's switch up to main sometime...)