NEWS

7/13/2007: Version 0.8.0 is out!

New in this release:

These fixes have been collecting for a while. Now you all get to enjoy them too.

The version number has been changed to reflect that the currect code is stable, yet is still missing some features which would be necessary for a 1.0 release


2/27/2006: Version 0.1.16 is out!

New in this release:

Just a few cleanups, nothing too major.


2/23/2006: Version 0.1.15 is out!

New in this release:

All bugfixes here, no new features.


12/25/2005: Version 0.1.14 is out!

New in this release:


7/18/2005: Version 0.1.13 is out!

New in this release:


5/7/2005: Version 0.1.12 is out!

New in this release:


5/5/2005: Version 0.1.11 is out!

New in this release:

Current items being worked on for the next release and later are:

You must run cdvupgrade on any clients and servers for this release. Note that it is much faster to do fresh checkouts than to upgrade clients.


4/13/2005: Mailing list and self-hosting repository

There's a public mailing list up now. If you have questions or want to partipate, send mail to devel at codeville dot org. The todo list is a good place to get started for helping out. More things will be added to it soon. [list info]

The self-hosting repository which has existed since February of 2004 has been opened to the public. URL is cdv://codeville.org/codeville/devel. Username 'anonymous' and the password is blank.

I have to put in a note of thanks here to the folks at Mosuki. They have been using it in production since June of 2004 and done an excellent job of finding bugs, stessing the system and pointing out where the interface needs improvement.

Also of note, the next version will probably be under the BSD license.


1/24/2005: New documentation

A client reference page has been added to the documentation. Thanks to Keith Irwin for writing this up.

If it seems like releases have been slowing down, then you're impatient. Geez, don't I get to take a vacation? In actual fact, they have slowed down a bit. Partially, this is due to stability. Since nothing has been really broken, I've been working on other things. Some architectural design work has also been happening behind the scenes. The next release will require a history rewrite in order to address some non-critical, long standing bugs and to regain some performance. Assuming that is as stable as the recent release, I will get back to adding all those planned useful features.


12/11/2004: Version 0.1.10 is out!

The critical bug is somewhat difficult to trigger, so it is unlikely that others have run into it. If you see tracebacks with 'merge error', this is what happened. Unfortunately, you have to figure out where it happened and throw away all the changes after that. Apologies, this is the first time something like this has happened in about 8 months.

In this release, the bug is mostly worked around. A proper fix will be in the next release. It will also fix some nuisance bugs with the merge algorithm and eliminate the false positives when doing 'history' on specific files. Potentially, performace will be better, as well.

Running 'rebuild' is required after upgrading.

Documentation is imminent. I promise.


9/21/2004: Version 0.1.9 is out!

The first 2 bugs caused significant problems in the previous release for branching and merging. Otherwise, this is mainly a small cleanup release.

The new feature of 'history' only showing changes for files you're interested in will occasionally give a false positive match. This will be fixed in a future release. It will also show changes in which the file was merged but not directly modified.


8/12/2004: Version 0.1.8 is out!

WARNING: The last bug fix requires a rebuild. Run 'rebuild' in your clients and start the server with -r the first time you run it.

WARNING: Be careful with the 'construct' command! It will throw away all your local changes without asking. It is also pretty fragile. Cleanup will happen for the next release.

Overall, this release eliminates roughly 30% of the CPU work.

As mentioned briefly above, there is now an offline mode. This is automatic when no repository is set. 'commit' will always be run with the -n switch, 'diff' will diff against the last commit, etc.


7/21/2004: Quick bugfix release 0.1.7.1 pushed.
There was a dumb bug which caused a traceback when using the internal diff in the previous release. Also a server traceback on post-commit actions.


7/20/2004: Version 0.1.7 is out!

Lot's of polish has been done recently, I'll be back to core features pretty soon. And documentation. Really. I promise.

Work done on supporting wildcard expansion will, probably in the next release, allow glob expansion for those poor souls using Windows without a shell to do it for them.

The list of regular expressions to ignore should be in the file CVILLE/ignore. One per line. They must match the entire path name of the file to apply. So if you want to ignore all files ending with ~, you would say '.*~'.

Keep in mind that the ignore patterns are also used by 'add' when expanding the '...' wildcard. You may still add files ignored by the expressions by explicitly naming them on the command line.


7/6/2004: Version 0.1.6 is out!

The new agent supports exactly the same command line interaction as ssh-agent. It's basically transparent. If the enironment variables are set, then clients will only ask for a password if they can't log in using the agent. The password is then automatically added to the agent.

There's no way the agent will work on windows. At least for now, sorry.

Because of the crypto changes, it is not possible to mix and match new and old clients and servers.


6/18/2004: Version 0.1.5 is out!

Be sure to read the server reference, there are significant changes.

Python 2.3 is now required. There's too much useful stuff in there and I'm only going to use more of it in the future.


6/8/2004: Version 0.1.4 is out!

Once again, mostly a bugfix release. Most of the new features implemented were in support of bug-fixing activities.

When upgrading, you will need to run the server with the -r switch the first time. You will also have to run

cdv rebuild
in all clients.

The server now supports a backup mode. When started with -b, only updates from other servers can be committed. In addition, only incremental backups on an existing backup are allowed. The way to use a backup server is create repositories as usual, then in a client update from the repository you want to backup, then commit to the backup server repository.


5/27/2004: Version 0.1.3 is out!

This is largely a bugfix release. Notably, this one should be useful under Windows. You will still have to execute as:
C:\Python23\python.exe C:\Python23\Scripts\cdv.py ...
Wildcard expansion doesn't work on Windows yet.

A fairly elegant cherry-picking scheme has been worked out, but will have to wait until more of the basic functionality is implemented.

I have upgraded my machine and am now using python 2.3. From now on, the rpm packages I make available will be for python 2.3. Please report problems with python 2.2 to me, as the current plan is to continue supporting it.


4/19/2004: Version 0.1.2 is out!

Old clients will no longer work, the backend format has changed. Neither will old servers. To convert your server, first create a new directory where the new server will reside. Then run:
cdvupgrade old_server_dir/ new_server_dir/
Then copy over the codeville_repository and passwd files.


3/3/2004: New release version 0.1.1 is out!


3/3/2004: Slides from the Codecon presentation are up.


2/6/2004: If you are using an older version update NOW! There was a serious bug in some of the DAG code. Do not reuse your old repositories or clients. If you need to recover them, let me know and I'll write a conversion tool. The command line syntax for commit and update has changed, please look through the quickstart.

Bram and Ross