1
1
What's changed in loggerhead?
2
2
=============================
7
- Loggerhead is no longer a TurboGears application, but rather a
8
WSGI application built using Paste (see http://wsgi.org/ and
9
http://pythonpaste.org/ for more about WSGI and Paste). XXX more.
11
- zpt.cleaner_urls bug 138021 ("loggerhead should generate links
12
based on revision numbers and file paths"). XXX more.
14
- The scripts no longer insist on Python 2.4 -- loggerhead works
17
- Bazaar as of version 1.5 has improved in performance enough that
18
the revision cache no longer gave any noticeable benefit, so it
19
was removed (the files-changed cache is still useful).
21
- The templates were rewritten in Zope's TAL markup, powered by
22
the simpleTAL library -- improving both the performance and
23
memory consumption of rendering by a factor of around 3 for
24
large pages over the old Kid templates.
26
- Loggerhead's poorly performing text index was disabled.
28
- Loggerhead no longer depends on bzrlib functions deprecated in
29
Bazaar 1.5 and removed in 1.6 (Martin Albisetti).
31
- The daemonization code was made more regular, fixing bugs
32
#139161 ("Starting loggerhead process may not close its stdin
33
and stdout properly") and #211526 ("Codebrowse log directory has
34
unnecessarily permissive permissions")
36
- Some confusion about what the 'file_id' query argument means was
37
cleared up: filter_file_id now means "filter revisions to those
38
that affect this file" in all views and file_id means "examine
39
this file/directory" in the annotate and inventory views.
41
- Dates are present more compactly.
43
- The loggerhead.conf file can specify which network interface to
44
bind to (Mattias Eriksson)
49
- The changelog view was out of order when not using the revision
7
55
- Michael Hudson <michael.hudson@canonical.com> has mostly taken
23
71
- Much dead code was removed.
25
73
- Loggerhead now computes the files changed between revisions only
26
when it needs to know this, which is a fairly expensive
27
operation in Bazaar. This massively improves performance and
28
memory usage in some situations.
74
when it needs to know this. This is a fairly expensive
75
operation in Bazaar, and doing it less massively improves
76
performance and memory usage in some situations.
30
78
- Loggerhead now takes a read lock on the branch being viewed for
31
79
the duration of each request, which improves performance
38
86
- The creation of History objects is much faster for large
39
87
branches (Aaron Bentley).
89
- Allow the construction of URLs using revnos and file paths as
90
well as revids and fileids (bug #98826):
92
- For changes pages, append the newest revno to display to the
93
URL, like http://.../changes/<revno>
95
- For annotate pages, append the revno to display to the URL,
96
followed by the path, like http://.../annotate/<revno>/<path>
98
- For file listing and revision pages append the revno to
99
display to the URL, like http://.../files/<revno>
101
Loggerhead still generates URLs using revision and file ids for
41
104
- Many bugs were fixed:
43
106
- Loggerhead does not escape special characters when embedding a
44
107
revision ID in a URL (bug #88286)
46
- Improved robustness ines the face of ghosts.
109
- Improved robustness in the face of ghosts.
48
111
- Don't crash on displaying a commit with an empty message (bug
57
120
- Loggerhead atom feeds expose internal hostname (James
58
121
Henstridge, bug #93585)
60
- Allow the construction of URLs using revnos and file paths as
61
well as revids and fileids (bug #98826)
63
123
- loggerhead don't like page break character (0x0C) in text
64
124
files (bug #113313)