| | 1 | = Version Control Cache = |
| | 2 | |
| | 3 | A redesign of the cache is needed for several reasons, among which the major ones are: |
| | 4 | 1. '''need to adapt to MultipleRepositorySupport.''' [[br]] |
| | 5 | Since multiple repositories can be accessed in a given environment, |
| | 6 | each of them should have the possibility to be supported by a cache. |
| | 7 | 2. '''need to adapt to different vc backends.''' [[br]] |
| | 8 | Now that Trac becomes more and more used with VCS other than Subversion, |
| | 9 | each backend should be able to use its own special kind of cache. |
| | 10 | A reasonably common base class (or set of base classes) should be |
| | 11 | nevertheless provided. |
| | 12 | 3. '''need to adapt to non-linear changeset history backends.''' [[br]] |
| | 13 | The vc cache must be able to adapt to backends where each changeset |
| | 14 | can have multiple parents and children changesets. |
