2010-10-21 20:27:00
Veracity Status Report, Version 0.5
Veracity 0.5 has been released.
What Changed in 0.5
- Full 64-bit support
- Core performance improvements:
- More efficient changeset format
- Better caching of working folder status
- Massive DAG-walking speedup, affecting update, push, pull, etc.
- Repository instance revision numbers (like hg's)
- Web UI improvements:
- Lots of performance improvements, particularly the activity stream
- Improved burndown chart accuracy
- Friendlier layout for adding and editing bugs
- Graphical DAG for source history
- Layout improvements viewing changesets
- Improved progress indicators throughout
- Bug relationships: blocks, depends on, duplicates
- Internet Explorer 8+ compatibility
- Merge improvements
- Default integration with SourceGear Diffmerge
- Resolve handles additional divergent move/rename/delete cases
- Building from source, particularly on Windows, has gotten easier.
- In progress:
- Integration with other diff/merge tools
- Repository packing
- REST API port to server-side Javascript
- Compatibility: Since the 0.3 release in July, most everything has changed.
- The repository format has changed.
- The layout of .sgdrawer in working copies has changed.
- The contents of ~/.sgcloset has changed.
- REST APIs, including those used by push/pull/clone, have changed.
- Repositories created with 0.3 will not work with 0.5, and vice versa.
- Settings saved in .sgcloset by older builds may not show up 0.5.
- Working copies should be recreated with the new version.
- Clients and servers must be the same version to play nice together.
Looking Ahead to 1.0
We now have a plan for the release of Veracity 1.0.
In a nutshell, look for a feature-complete beta release around the end of January. That'll be the time when we freeze the repo storage formats and also deploy a public Veracity server.
The final release will occur whenever the beta feature set is clean and solid. We're hoping that occurs in April, but it'll happen when it happens. We're not going to call this thing 1.0 until we have lots of confidence that it can be trusted.
The following table should answer some of the questions about what will be in 1.0 and what will not.
|
Feature |
In Veracity 1.0? |
|
Command-line app |
Yes |
|
All basic source control operations (checkout, commit, push, pull, tag, diff, history, etc) |
Yes |
|
Integrated Scrum package with web UI |
Yes |
|
Embedded web server |
Yes |
|
Tortoise Windows shell integration |
Yes |
|
Named branches |
Yes |
|
Subrepositories (like git submodules or svn externals) |
Yes |
|
Digital signatures, logins, user accounts |
Yes |
|
File locks (optional, not when disconnected) |
Yes |
|
Deltified storage using VCDiff |
Yes |
|
Build tracking (which bugs were fixed in this build?) |
Yes |
|
Visual Studio plugin |
Later |
|
Eclipse plugin |
Later |
|
Repo storage in SQL Server |
Later |
|
Repo storage in PostgreSQL |
Later |
|
IIS integration |
Later |
|
Apache integration |
Later |
|
Rebase |
Later |
|
Pre/Post Commit Hooks |
Later |
Everything we release in the 1.0 timeframe will be part of Veracity Core, fully open source under the Apache License 2.0. At some point later, we will be selling proprietary add-ons, but Veracity Core will always be open source and will be a complete and useful feature set.