Status
Development Roadmap
Met:
- Milestone 1 (20 Oct 2000): Basic working copy manipulation;
client can checkout/update/commit using XML files.
- Milestone 2 (15 May 2001): Rudimentary working filesystem;
client can checkout/update/commit using WebDAV layer.
- Milestone 3 (Thu 30 August 2001): Subversion is now
self-hosting; see the Project
Source page for details.
- Milestones 4 and 5 (Fri 19 Oct 2001): These milestones
lwere reached together, and fix various bugs related to properties,
networking, and filesystem deltification.
- Subversion 0.6 (Milestone 6) (Mon 12 Nov 2001): Complete
"svn log", and have "svn mv",
"svn cp" working at least on files, with directory
support optional (for this milestone, that is, not in the long term).
- Subversion 0.7 (Mon 3 Dec 2001): Branching and tagging.
- Subversion 0.8 (Mon 14 Jan 2002): Commit system rewrite (issue
#463); diffs over the network in both directions (issue
#518); newline conversion and keyword substitution (issue
#524); and code migration from libsvn_fs to libsvn_repos (issue
#428).
Upcoming:
- Subversion 0.9 (Mon 11 Feb 2002):
"svn switch" (
issue #575); resolution of some repository db stability
issues (issue
#608); and many small features and bugfixes since 0.8, all
praise to the Conquering Developer Hordes. See upcoming CHANGES
file for details.
- Subversion 0.10: "svn merge"
- Alpha (TBD): Most commonly used features completed.
- Beta (TBD): Release candidate, heavy
testing. Possible inclusion of newer, less popular features.
- 1.0 Release (TBD): Release.
Recently, milestones are being set as short timelines (around
three weeks), with a few key features. We will be doing plenty
of bug fixing and other work during the development towards a
milestone, but "meeting a milestone" requires the specified
features to have been implemented.
Progress
(note: these meters measure nothing but fuzzy gut feelings. :-) )
| Versioning Filesystem |
|
| Networking Layer |
|
| Client Libraries |
|
| CVS Migration Tools |
|
| Documentation |
|
| Tests |
|
Recent Activities
Much bug swatting and patch review, plus work toward the latest
milestone. Committers are trying to place a higher priority on patch
review & response, as the project has reached the stage where
increasing parallelization of development will bring faster progress.
The Big Picture
(taken from the design
document)
