Developers' Guide - Template versioning.

VERIFIED WONTFIX

Status

()

Bugzilla
bugzilla.org
--
enhancement
VERIFIED WONTFIX
17 years ago
11 years ago

People

(Reporter: CodeMachine, Assigned: Nobody's working on this, feel free to take it)

Tracking

Details

(Reporter)

Description

17 years ago
Please specify below the relevant information about template versioning,
including when to increase the version, how to insert versions into templates, etc.

This is needed for the developers' guide.
(Reporter)

Updated

17 years ago
Priority: -- → P1
Target Milestone: --- → Bugzilla 2.16
Attempt 1:

Every template shipped with Bugzilla has a version number at or near the top,
e.g. <!-- 1.0@bugzilla.org --> . If you customise a template, you should keep
the same version number in the custom template, and add your own domain name.

On occasion, the version numbers of the Bugzilla-shipped templates will change.
This version number has a major part and a minor part.

If the major part changes, that means the interface to this template is
incompatible with the interface to previous templates. Bugzilla will note this
incompatibility and tell you about it.

If the minor part changes, the interface is backwardly-compatible, but there are
some changes you should investigate and consider also making in your custom
templates.

For those templates with INTERFACE comments, you can use CVS to see the
differences in this section of the file, to get an rundown on what has changed
about the template interface.

Gerv

Comment 2

17 years ago
Also, make sure to note that template version strings in templates which 
are not html should be wrapped in TT comments.
(Reporter)

Comment 3

16 years ago
OK, I updated the Guide with the appropriate details.  Please check it.

Gerv, the stuff you mentioned is for administrators, this is the developers'
guide.  Take the admin stuff to bug #147137.

If you're happy with what's been written, feel free to close this out, otherwise
let me know what still has to be done.

Comment 4

16 years ago
Bugzilla uses Template Toolkit 2 (tt2) which is available http://www.tt2.org/.
Bugzila version X requires TT version X. There is no need to install tt2
seperately, it is included with your install of bugzilla. The included version is X.

Please find the docs at this URL: 
http://www.template-toolkit.org/docs.html



Err..

Bugzilla doesn't come with TT. Bundle::Bugzilla brings it in from CPAN, but
thats not the same thing.

Comment 6

16 years ago
Ok, so that should be ammended. I'm just concerned that users should know where
to seek documentation on the syntax of these templates.

Comment 7

16 years ago
ping
MattyT: status?
QA Contact: matty → justdave
If this is for developers only, it's not a blocker on the 2.16 release.

Gerv
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Let's get this in...
Assignee: matty → gerv
Blocks: 107917
Priority: P1 → --
What this bug actually now represents (if anything) is:

The latest ideas for template versioning are that we always use TT comments. The
Developers Guide does not reflect this. It should.

Gerv
Assignee: gerv → mattyt-bugzilla

Comment 12

13 years ago
In order for this to be actually useful, there has to be some easy way for the
admin to find out which version numbers have changed. Until we come up with
that, the template versioning isn't very useful.
Assignee: mattyt-bugzilla → nobody
Severity: normal → enhancement
Target Milestone: Bugzilla 2.18 → Bugzilla 2.22

Comment 13

13 years ago
The trunk is now frozen to prepare Bugzilla 2.22. Only bug fixes are accepted, no enhancement bugs. As this bug has a pretty low activity (especially from the assignee), it's retargetted to ---. If you want to work on it and you think you can have it fixed for 2.24, please retarget it accordingly (to 2.24).
Target Milestone: Bugzilla 2.22 → ---
Assignee: nobody → justdave
QA Contact: justdave → default-qa
Assignee: justdave → nobody

Comment 14

11 years ago
The version comments have been removed from the templates, so this can be resolved, I guess...
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX

Comment 15

11 years ago
yes
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.