Skip to content

Branch management #3916

Closed
Closed
@xordoquy

Description

@xordoquy

I'm a bit annoyed with the current branch management with DRF at the moment.

I'd like to drop master for the stable branch.

What I have in mind is and basing myself on 3.3.2 being the latest stable:

  • master becomes the base branch for the next minor release (say 3.4.0) with new features & deprecation.
  • create a "stable" 3.3.x branch which will be used for all the micro release (bug fixes only).
  • have an exploratory 4.x branch for the next major if any.

The major advantage is that we will improve a lot stability by keeping the current stable release restricted to bug fixes and have new micro for new features.
The major concern will be it'll require a bit more work to back port things

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions