Changes between Version 32 and Version 33 of MultipleRepositorySupport
- Timestamp:
- Jan 26, 2010, 11:37:14 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MultipleRepositorySupport
v32 v33 29 29 30 30 == Related Tickets == 31 [[TicketQuery(group=status,order=priority,col=summary|component|milestone,format=table,keywords=~multirepos)]]31 ![[TicketQuery(group=status,order=priority,col=summary|component|milestone,format=table,keywords=~multirepos)]] 32 32 33 33 == Installation (with mercurial) == … … 92 92 93 93 == TODO == 94 === Merge === 95 96 Now with #7116 nearly done, it's time to plan the merge. 97 98 * 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"]: 99 - mainly what they need to do for adapting their repository hooks 100 - 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) 101 - trac-admin (repository and changeset commands) 102 - hidden and url attributes 103 - admin panel intro 104 * anything else? 105 106 Not strictly needed before the merge but would be nice: 107 - #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. 108 94 109 === Major === 95 110 - 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 102 117 (but works fine for every other web browser, including Firefox 3) ~~ FF 2 is now dead, isn't it? 103 - "normal" feature: it's currently not possible to compare across repositories 118 - "normal" feature: it's currently not possible to compare across repositories (#4048) 104 119 (the situation is detected, but raises a "not implemented" error). 105 120 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]] 109 124 Bonus points if that cache is smart enough to handle multiple scoped repositories without data duplication. [[br]] 110 A second (much) more ambitious step would be to generalize the cache so that it can support other (d)vcs .125 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. 111 126 112 127 === 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. 145 160 - 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? 161 * there's a `.hidden` flag now (and a corresponding `hidden` attribute on Repository that can be set via the admin panel or via: 162 {{{ 163 trac-admin ... repository set hidden true 164 }}} 146 165 147 166 > Other than that, so far this is going to meet my needs quite nicely. Thanks!