Opened 13 years ago
Closed 12 years ago
#17919 closed Cleanup/optimization (fixed)
Release process could use some more detail about beta and release candidates
Reported by: | Preston Holmes | Owned by: | Aymeric Augustin |
---|---|---|---|
Component: | Documentation | Version: | dev |
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.
Change History (6)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 13 years ago
comment:3 by , 12 years ago
Triage Stage: | Design decision needed → Accepted |
---|
Perhaps now would be a good time to add these details.
comment:4 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Tentatively assigning to myself.
comment:5 by , 12 years ago
Has patch: | set |
---|
This pull request, among other things, fixes this ticket: https://github.com/django/django/pull/816
comment:6 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Replying to ptone:
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