1
1
What's changed in loggerhead?
2
2
=============================
7
- Download a diffs between revisions. (Martin Albisetti)
9
- Modified templates to make loggerhead's theme easier to
12
- Default sqlite interface is now sqlite3. (Robert Collins)
14
- New ninja theme sponsored by Canonical (Martin Albisetti)
16
- Added COPYING file and clarified copyright headers (John Arbash Meinel)
18
- Remove the .py extension requiered by the Debian Policy.
21
- New startup script serve-branches will serve Loggerhead without
22
the need of configuration, and allow you to browse through directories
23
and branches. (Michael Hudson)
25
- Loggerhead is no longer a TurboGears application, but rather a
26
WSGI application built using Paste (see http://wsgi.org/ and
27
http://pythonpaste.org/ for more about WSGI and Paste).
29
- URLs now use revision numbers instead of revision ids (Martin Albisetti)
31
- The scripts no longer insist on Python 2.4 -- loggerhead works
34
- Bazaar as of version 1.5 has improved in performance enough that
35
the revision cache no longer gave any noticeable benefit, so it
36
was removed (the files-changed cache is still useful).
38
- The templates were rewritten in Zope's TAL markup, powered by
39
the simpleTAL library -- improving both the performance and
40
memory consumption of rendering by a factor of around 3 for
41
large pages over the old Kid templates.
43
- Loggerhead's poorly performing text index was disabled. bzr-search
44
is now used if the plugin is installed and a text index is present
45
on the branch being viewed. (Martin Albisetti, Robert Collins).
47
- Loggerhead no longer depends on bzrlib functions deprecated in
48
Bazaar 1.5 and removed in 1.6 (Martin Albisetti).
50
- The daemonization code was made more regular, fixing bugs
51
#139161 ("Starting loggerhead process may not close its stdin
52
and stdout properly") and #211526 ("Codebrowse log directory has
53
unnecessarily permissive permissions")
55
- Some confusion about what the 'file_id' query argument means was
56
cleared up: filter_file_id now means "filter revisions to those
57
that affect this file" in all views and file_id means "examine
58
this file/directory" in the annotate and inventory views.
60
- Dates are present more compactly.
62
- The loggerhead.conf file can specify which network interface to
63
bind to (Mattias Eriksson)
68
- The changelog view was out of order when not using the revision
73
7
- Michael Hudson <michael.hudson@canonical.com> has mostly taken
74
8
over the maintenance of loggerhead.
89
23
- Much dead code was removed.
91
25
- Loggerhead now computes the files changed between revisions only
92
when it needs to know this. This is a fairly expensive
93
operation in Bazaar, and doing it less massively improves
94
performance and memory usage in some situations.
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.
96
30
- Loggerhead now takes a read lock on the branch being viewed for
97
31
the duration of each request, which improves performance
104
38
- The creation of History objects is much faster for large
105
39
branches (Aaron Bentley).
107
- Allow the construction of URLs using revnos and file paths as
108
well as revids and fileids (bug #98826):
110
- For changes pages, append the newest revno to display to the
111
URL, like http://.../changes/<revno>
113
- For annotate pages, append the revno to display to the URL,
114
followed by the path, like http://.../annotate/<revno>/<path>
116
- For file listing and revision pages append the revno to
117
display to the URL, like http://.../files/<revno>
119
Loggerhead still generates URLs using revision and file ids for
122
41
- Many bugs were fixed:
124
43
- Loggerhead does not escape special characters when embedding a
125
44
revision ID in a URL (bug #88286)
127
- Improved robustness in the face of ghosts.
46
- Improved robustness ines the face of ghosts.
129
48
- Don't crash on displaying a commit with an empty message (bug
added
removed
NEWS
