Release process could use some more detail about beta and release candidates

[Preston Holmes]

I think it is a bit unclear about what counts as a qualifying change later in the release cycle.

​https://docs.djangoproject.com/en/dev/internals/release-process/#release-cycle

The three phases don't shed much light about what kind of bugs can be filed for alpha, beta, and RC stages

In general I think the feeling is that only Release Blockers/Regressions should be committed at RC stage?

However, in many projects - alpha implies not feature frozen, however that is what is stated by the docs by saying that alpha marks transition from feature adding, to bug fixing.

As the core team increases - having a little clarification in the docs would help.

[Preston Holmes]

Replying to ptone:

The three phases don't shed much light about what kind of bugs can be filed for alpha, beta, and RC stages

This was not stated correctly - I mean what kinds of bug patches can be committed (blockers vs other bugs)

Obviously bugs can be filed at any time

[Tim Graham]

Perhaps now would be a good time to add these details.

[Aymeric Augustin]

Tentatively assigning to myself.

[Aymeric Augustin]

This pull request, among other things, fixes this ticket: ​https://github.com/django/django/pull/816

[Aymeric Augustin <aymeric.augustin@…>]

In 5d883589a8f6950e98538c9509a201d61573460d:

Updated the release process docs to reflect the current practices.

Fixed #17919.