Code

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#11201 closed (invalid)

Does the docs to 1.0 really point to 1.0?

Reported by: waltercruz Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: wrong symlink Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Editing the howto/deploy/index.txt from a 1.0.2 package, I see:

:ref:Deploying under mod_python <howto-deployment-modpython> is the
recommended deployment method; start there if you're not sure which path you'd
like to go down.

But both pages, for trunk http://docs.djangoproject.com/en/dev/howto/deployment/#howto-deployment-index and http://docs.djangoproject.com/en/1.0/howto/deployment/ point mod_wsgi as a default method...

Is the docs to 1.0 on django site pointing to trunk too?

Attachments (0)

Change History (3)

comment:1 Changed 5 years ago by Alex

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

It uses the 1.0.X branch. Please don't use trac for asking support questions.

comment:2 follow-up: Changed 5 years ago by waltercruz

Ok, Sorry me. But, shouldn't the online docs to 1.0 point to the latest released 1.0 series (in the case, 1.0.2), or I am wrong to suppose that?

comment:3 in reply to: ↑ 2 Changed 5 years ago by kmtracey

Replying to waltercruz:

Ok, Sorry me. But, shouldn't the online docs to 1.0 point to the latest released 1.0 series (in the case, 1.0.2), or I am wrong to suppose that?

They point to better than that -- 1.0.X branch has all improvements made to doc since 1.0.2 was released. Why would you not want to see those? 1.0.X is bugfix only, so there is no possibility of confusion resulting from online doc of function that isn't in the release you have, the only things you are seeing online that aren't in the shipped release version are doc improvements for the released function. If for some reason you really want to see doc as it existed in the release, you can use the copy that is in the release package you are using.

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.