Changes between Version 32 and Version 33 of MultipleRepositorySupport

Timestamp:

Jan 26, 2010, 11:37:14 AM (14 years ago)

Author:

Christian Boos

Comment:

#Merge tasks

MultipleRepositorySupport

@@ -29 +29 @@
 
 == Related Tickets ==
-[[TicketQuery(group=status,order=priority,col=summary|component|milestone,format=table,keywords=~multirepos)]]
+![[TicketQuery(group=status,order=priority,col=summary|component|milestone,format=table,keywords=~multirepos)]]
 
 == Installation (with mercurial) ==
@@ -92 +92 @@
 
 == TODO ==
+=== Merge ===
+
+Now with #7116 nearly done, it's time to plan the merge. 
+
+ * What remains to be done is mainly documentation, as when people using `trunk` will get the multirepository changes, they'll need to find out what to do, in ["0.12/TracRepositoryAdmin"]:
+   - mainly what they need to do for adapting their repository hooks
+   - what they can do with their default repository (setting up an alias for default, or better, "migrating" their unnamed default repository to a named repository and add an alias to the empty repo pointing to the new name)
+   - trac-admin (repository and changeset commands)
+     - hidden and url attributes
+   - admin panel intro
+ * anything else?
+
+Not strictly needed before the merge but would be nice:
+ - #7743 for mercurial - should add a contrib file there, containing a `hook` function calling the Trac API appropriately, and have an example of a command hook calling trac-admin directly. 
+
 === Major ===
  - split repository names at "/" in the repository browser (i.e. show only the ''a'' entry at toplevel when we have repositories `a/one` and `a/two`, show ''one'' and ''two'' when expanding ''a'')
@@ -101 +116 @@
    where the changeset icon doesn't align properly to the right 
    (but works fine for every other web browser, including Firefox 3) ~~ FF 2 is now dead, isn't it?
- - "normal" feature: it's currently not possible to compare across repositories 
+ - "normal" feature: it's currently not possible to compare across repositories (#4048)
    (the situation is detected, but raises a "not implemented" error). 
    It would be quite useful to be able to do so, and it's doable without much work 
@@ -108 +123 @@
    ~~In a first step, the existing cache could be adapted to simply handle more than one repository.~~ [[br]]
    Bonus points if that cache is smart enough to handle multiple scoped repositories without data duplication. [[br]]
-   A second (much) more ambitious step would be to generalize the cache so that it can support other (d)vcs.
+   A second (much) more ambitious step would be to generalize the cache so that it can support other (d)vcs, but this is somewhat out of scope of the MultiRepos task itself.
 
 === Minor Points ===
@@ -144 +159 @@
  - one possibility would be to not list aliases (even aliases for the `[trac] repository_dir`). I think that's acceptable, but there should be an easy way to learn about the defined aliases, maybe they can be listed at the bottom of the toplevel page.
  - OTOH, aliases might be defined simply because they are more convenient names than the "real" ones, so in the end, more flexibility is needed. Add a `.browseable` flag, a la Samba?
+   * there's a `.hidden` flag now (and a corresponding `hidden` attribute on Repository that can be set via the admin panel or via:
+     {{{
+     trac-admin ... repository set hidden true
+     }}}
 
 > Other than that, so far this is going to meet my needs quite nicely. Thanks!