Hi,

I'd like to resume my work on the version control refactoring.

The items I want to address this time are:
* fixing #1830 (Repository subsets have to be fully self contained)
  For this, I think returning 'None' in place where we used
  to raise a 'TracError: no such changeset or no such node'
  would be enough. Of course, many places in the code would
  have to be adapted to handle this situation, so I guess this
  is potentially disruptive.
* reintroduce the support for additional changeset properties
  ([2649] and adding Changeset.get_properties() method)
* reintroduce the support for tags and branches
  ([2648] and adding Repository.get_tags() and
  Repository.get_branches()).
  Tag and branch support in svn could be added by using a
  [subversion] configuration section, where tags and branches
  could be listed (defaults would be e.g. tags/* and branches/*).
* make the changeset link syntax more tolerant (at least allow
  hexadecimal changeset numbers)

When this is done (should not take long),
this could eventually be merged back.

Then, some more important changes:
* rework the interaction with the cache.
  The cache could be used for more operations:
  * for the Repository.get_changes() (changesets in a
    given period of time)
  * for the Repository.get_path_history (maybe)
  * for the Repository next_rev and previous_rev (maybe)
  * for the Node information (currently not used, but would
    be crucial for "flat" versioning systems like mercurial)
* (eventually) rework the TracLogRevision to support multiple
  ''branches'' (similar to gitk/hgk)

Also, there shouldn't be much (if any) interference with
the work done on other branches (WSGI, anti-spam, etc.)

-- Christian
_______________________________________________
Trac-dev mailing list
Trac-dev@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-dev

Reply via email to