Roadmap
-
CvSync may has been a nice tool, but it's user interface was somewhat cryptic. Version 0.8 had three different ways of storing the state information, and tried to be flexible introducing several command line options as well as an interactive session... This was crazy, and Tailor VersionOne will try to fix the mess, with some other nice goals:
- Make it possible to attach arbitrary transforms to the changesets once they are applied and before committing them to the target VC; refilling of the log message, remapping author's names, and in general apply any needed fixup.
- Make it easier to set up a double way bridge
- Remove interactive session machinery: it was funny, but definitely out of scope.
VersionOne is mostly done: last missing piece is TwoWaySync.
-
It's time to start thinking about new directions...
- better separation of "low level" stuff (ie, move such methods on the Repository class)
- several people asked about a "VC-neutral" representation of patches: I'd really like to propose such format (I'm biased toward YAML)
- better handling of branches: at the very least, I'd like to be able to tailorize a new branch, having already a tailorized trunk of the same repo
Note: See
TracRoadmap for help on using
the roadmap.
