368801 - autogenerated docs should list the correct tag for the corresponding version

Status: RESOLVED WONTFIX

(Bugzilla :: Documentation, enhancement, P4)

Description

[timeless]

3.13.2.1. Upgrading using CVS
Every release of Bugzilla, whether it is a point release or a bugfix, is tagged in CVS. Also, every tarball that has been distributed since version 2.12 has been created in such a way that it can be used with CVS once it is unpacked. Doing so, however, requires that you are able to access cvs-mirror.mozilla.org on port 2401, which may not be an option or a possibility for some users, especially those behind a highly restrictive firewall. 


 If you can, updating using CVS is probably the most painless method, especially if you have a lot of local changes. 
 

The following shows the sequence of commands needed to update a Bugzilla installation via CVS, and a typical series of results. 

bash$ cd /var/www/html/bugzilla
bash$ cvs login
Logging in to :pserver:[e-mail]:2401/cvsroot
CVS password: ('anonymous', or just leave it blank)
bash$ cvs -q update -r BUGZILLA-2_18_1 -dP
P checksetup.pl
P collectstats.pl
P globals.pl
P docs/rel_notes.txt
P template/en/default/list/quips.html.tmpl
(etc.)
        
 
The example updates me to 2.18.1, I don't care that it's an example. it should be a useful example and that means it should update me to 2.20.x (where x = 0 or some number greater than 0, i don't really care which).

Comment 1

[Gervase Markham [:gerv]]

We now use git.

Gerv

Comment 2

[Frédéric Buclin]

This has nothing to do with git vs cvs.

The point is that the documentation gives a real example on how to install/upgrade Bugzilla, and so the version used in the example is hardcoded. But when you release new major versions, the example looks old as it mentions an old version. So the suggestion was to make the example dynamic, using the current version.