Changes between Version 50 and Version 51 of TracMercurial

Timestamp:

Jan 19, 2009, 11:30:26 AM (15 years ago)

Author:

Christian Boos

Comment:

update to current releases (r7744 / r7757)

TracMercurial

@@ -2 +2 @@
 = Mercurial Plugin for Trac (#1847) =
 
-There is an '''experimental''' plugin for Trac [milestone:0.10] and  Trac [milestone:0.11]
-which enables [http://www.selenic.com/mercurial Mercurial] 
-to be used instead of [http://subversion.tigris.org Subversion]
+This a plugin for Trac which enables 
+[http://www.selenic.com/mercurial Mercurial] 
+to be used instead of [http://subversion.tigris.org Subversion] 
 as the VersioningSystemBackend for Trac.
 
-''The plugin being experimental, expect some rough edges
-and a somewhat unstable set of features/documentation...''
-
-Change Logs: 
+''The plugin has been marked as experimental for a while, but even if there are still some rough edges here and there, it's gotten quite usable.''
+
+Please take care to use a recent version of the plugin before reporting issues.
+See the [#Releases version table] below.
+
+Detailed Change Logs: 
  * log:sandbox/mercurial-plugin
  * log:sandbox/mercurial-plugin-0.11
@@ -76 +78 @@
 ==== Releases ====
 || '''Version''' || mercurial-plugin || Trac vc-refactoring || Compatible with hg         ||
-|| '''0.12.0.5'''  || [source:sandbox/mercurial-plugin-0.12@7443] || [source:sandbox/multirepos] ('''not''' trunk) ||  1.0.x, 1.1.x, tip ||
-||'''0.11.0.6''' || [source:sandbox/mercurial-plugin-0.11@7442] || [milestone:0.11] or [source:branches/0.11-stable] ||  ''0.9.x'' (?), 1.0.x, 1.1.x, tip  ||
+|| '''0.12.0.6'''  || [source:sandbox/mercurial-plugin-0.12@7757] || [source:sandbox/multirepos] ('''or''' trunk) ^(1)^ ||  1.0.x, 1.1.x, tip ||
+||'''0.11.0.7''' || [source:sandbox/mercurial-plugin-0.11@7744] || [milestone:0.11] or [source:branches/0.11-stable] ||  ''0.9.x'' (?), 1.0.x, 1.1.x, tip  ||
+|| ''0.12.0.5''  || [source:sandbox/mercurial-plugin-0.12@7443] || [source:sandbox/multirepos] (''possibly'' trunk as well) ||  1.0.x, 1.1.x, tip ||
+||''0.11.0.6'' || [source:sandbox/mercurial-plugin-0.11@7442] || [milestone:0.11] or [source:branches/0.11-stable] ||  ''0.9.x'' (?), 1.0.x, 1.1.x, tip  ||
 || 0.11.0.4 || [source:sandbox/mercurial-plugin-0.11@7243] || [milestone:0.11] or [source:branches/0.11-stable] ||  0.9.x, 1.0.x, tip  ||
 || 0.10.0.2  || [source:sandbox/mercurial-plugin] (0.10) || [milestone:0.10]    ||  0.7, 0.8, 0.9  ||
@@ -85 +89 @@
 ||      0.1      ||       r2514      ||        r2511        ||  0.7, tip without 1d7d0c07 ||
 
-Note: 
+ 1. The 0.12 version has i18n support but there's currently a problem when deploying this plugin as an ".egg". Workarounds exists, see #7877.
+
+General Notes: 
  - '''the ''Compatible with hg'' column above needs to be updated''' [[br]]
    It is quite likely that some 0.9.x versions (maybe even 0.9.5) won't work anymore with the 0.11 and 0.12 versions of the plugin (i.e. those are the versions actively maintained). Most notably, since r7742 the `filectx` API is used, which means that versions anterior to hg:482c524dd9ab can't possibly work (0.9.1 ''could'' work - I should check). Anyway, at this time you should not be using a pre-1.0 version of Mercurial anymore.
@@ -283 +289 @@
 === To cache or not to cache? ===
 
-When you try TracMercurial on the kernel repo, you quickly realize
-that it's way too slow without a db!
-Also, the way the diffs are produced currently (i.e. by Trac, from the full 
-content of the files) is also too slow to be usable on such big repositories 
-(e.g. the kernel changeset fc66195f585a took 7 minutes to be displayed on my 
-machine). 
-See #2591.
+Recent versions of the plugin (r7744 for 0.11 or r7757 for 0.12) have a greatly improved browsing speed. It's now possible to navigate on repositories of the size of the Linux kernel repo.
+
+However, producing diffs or even gathering the timeline events for repositories of such size is still too slow.
+For the diffs, we could reduce the amount diffs generated (see #2591, #7975).
+For the timeline, we should really have a cache, not only for the performance issue but also because the current heuristic for retrieving the changesets in a given period of time doesn't always work (see r5365).
 
 === Cool Features ===
@@ -349 +353 @@
  * Log in as an user with `TRAC_ADMIN` permission, and look in the `Admin` pages, `General / Plugins`. Do you see the entry for the !TracMercurial plugin there? If yes, is the !MercurialConnector component enabled? 
 
+=== Known Issues ===
+
+[[TicketQuery(component=plugin/mercurial,milestone=not applicable,status=!closed)]]
 
 == Implementation Notes ==