Edgewall Software

Changes between Version 10 and Version 11 of VcRefactoring


Ignore:
Timestamp:
Mar 29, 2007, 4:16:10 PM (17 years ago)
Author:
Christian Boos
Comment:

stating some goals for 0.12

Legend:

Unmodified
Added
Removed
Modified
  • VcRefactoring

    v10 v11  
    55
    66[[PageOutline]]
     7
     8The major goals for [milestone:0.12] in the versioncontrol area will be:
     9 1. support for multiple repositories
     10 2. support for scm neutral cache
     11 3. ideally, if the GenericTrac approach is finalized, arbitrary properties,
     12    comments and attachments for changeset and path Trac resources (useful for
     13    code reviews)
    714
    815The forthcoming changes aim to be better support some
     
    1522[[TitleIndex(VcRefactoring/)]]
    1623
    17 See also the related Trac-Dev:161 thread.
     24The current controller changes are simple refactorings which are not changing the versioncontrol API, but cleaning up the internals of the versioncontrol related web ui.
     25Those changes could eventually go in 0.11.
    1826
    1927
     
    199207e.g. `node_changes_hg` (see also #2733).
    200208
     209
     210In addition, there will most certainly be the need for a kind of 
     211`revision_link` table in the general case, listing the prev/next
     212relations between revisions.
     213
     214Of course, a backend which only needs a sequential ordering for its
     215revisions should be able to bypass that table.
     216
     217
    201218----
    202219
    203 See also: [googlegroups:trac-dev:f32afb39eb3bfd87 improving bazaar support], discussed on Trac-Dev
     220See also: the original Trac-Dev:161 thread, [googlegroups:trac-dev:f32afb39eb3bfd87 improving bazaar support] on Trac-Dev