Code

Opened 2 years ago

Closed 14 months ago

#17919 closed Cleanup/optimization (fixed)

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

Reported by: ptone Owned by: aaugustin
Component: Documentation Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Attachments (0)

Change History (6)

comment:1 Changed 2 years ago by ptone

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

comment:2 in reply to: ↑ description Changed 2 years ago by ptone

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

comment:3 Changed 17 months ago by timo

  • Triage Stage changed from Design decision needed to Accepted

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

comment:4 Changed 14 months ago by aaugustin

  • Owner changed from nobody to aaugustin
  • Status changed from new to assigned

Tentatively assigning to myself.

comment:5 Changed 14 months ago by aaugustin

  • Has patch set

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

comment:6 Changed 14 months ago by Aymeric Augustin <aymeric.augustin@…>

  • Resolution set to fixed
  • Status changed from assigned to closed

In 5d883589a8f6950e98538c9509a201d61573460d:

Updated the release process docs to reflect the current practices.

Fixed #17919.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.