#8074 closed (invalid)
Remove 'new in development version' tags from docs
| Reported by: | Jeff Anderson | Owned by: | Jeff Anderson |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The django docs have many, many things marked "new in development version"
This will need to be updated to reflect the 1.0 release rather than the development version.
Another option would be to completely remove the "new in..." notes altogether.
Change History (6)
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The alpha/beta series are development releases. When 1.0 is released, the "new in development version" tags will be removed, and the documentation will be a complete and accurate reflection of v1.0. The right place for 'new in this release' descriptions is the release notes. This is consistent with the approach taken with past releases.
comment:3 by , 16 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
| Summary: | Change 'new in development version' to 'new in 1.0' → Remove 'new in development version' tags from docs |
| Triage Stage: | Design decision needed → Accepted |
Why close the ticket? This still describes a task that needs to be done-- remove the "new in..." tags in the Documentation for the 1.0 release.
comment:4 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
I've closed the ticket because removing that tag from the text is part of the standard release process, along with other tasks like 'make a 1.0 tarball' and 'increment the version number'. We (or to be precise, James) doesn't need a ticket to document well established release procedure.
Because there is a decision, marking DDN.
I will be happy to write the patch closer to the 1.0 release.