| 1 | = Version Control Refactoring = |
| 2 | |
| 3 | This branch is a sandbox for introducing new features |
| 4 | that are potentially disruptive. |
| 5 | |
| 6 | This is based on the previous refactoring and on the |
| 7 | TracDiff branch, both of them pretty much stable |
| 8 | and already integrated in the trunk for milestone:0.10. |
| 9 | |
| 10 | The forthcoming changes aim to be better support some |
| 11 | advanced version control system backends, like |
| 12 | [http://www.selenic.com/mercurial Mercurial]. |
| 13 | To that effect, the changes added to the core will be |
| 14 | exercised by jointly developing the TracMercurial plugin. |
| 15 | |
| 16 | See also the related |
| 17 | [http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/161 thread] |
| 18 | on the Trac Devel mailing list. |
| 19 | |
| 20 | == Support for Multiple scopes within a Repository == |
| 21 | |
| 22 | This basically means fixing #1830. |
| 23 | |
| 24 | |
| 25 | == Support for Mercurial-like Version Control System == |
| 26 | |
| 27 | === Basic Level === |
| 28 | * support for non-numerical changesets (start with hexadecimal digit support) |
| 29 | * support for extra changeset properties |
| 30 | |
| 31 | Those are the minimal changes needed so that the Mercurial plugin can work at all. |
| 32 | |
| 33 | |
| 34 | === Advanced Level === |
| 35 | |
| 36 | * Support for direct jump to a tag or a branch |
| 37 | * Support for arbitrary changeset names (e.g. `[tip]` or `[head]`) |
| 38 | |
| 39 | === Support for Big Repositories === |
| 40 | |
| 41 | This means extended cache support, and certainly needs some big changes |
| 42 | to the way caching is done. |
| 43 | |