Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#8074 closed (invalid)

Remove 'new in development version' tags from docs

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


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 Changed 7 years ago by programmerq

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

Because there is a decision, marking DDN.

I will be happy to write the patch closer to the 1.0 release.

comment:2 Changed 7 years ago by russellm

  • Resolution set to wontfix
  • Status changed from new to 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 Changed 7 years ago by programmerq

  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Summary changed from Change 'new in development version' to 'new in 1.0' to Remove 'new in development version' tags from docs
  • Triage Stage changed from Design decision needed to 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 Changed 7 years ago by russellm

  • Resolution set to invalid
  • Status changed from reopened to 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.

comment:5 Changed 7 years ago by programmerq

fair enough. :)

comment:6 Changed 4 years ago by jacob

  • milestone 1.0 deleted

Milestone 1.0 deleted

Note: See TracTickets for help on using tickets.
Back to Top