[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index


From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-06-11 16:43:10 CEST

Just thought the dev list would like to know what's been going on
lately in Subversion development, especially since we recently passed
our 1-year anniversary of creating the project in CVS (June 5th,
2000). I've also noticed that this list has over 200 addresses on it
now -- that's a lot of lurkers! :)

* Mike Pilato has been rewriting large parts of the working copy
  library. Versioning directories is difficult, and as a result we've
  had to come up with a more complex model of how to track items in
  the `entries' file. This is a huge task, because we're constantly
  coming up with new use cases ("how many ways can the user screw up
  the working copy *today*?") and trying to accomodate them.

* I have been working partially with Mike Pilato on these working copy
  issues, as well as documenting them in texinfo. Since the
  situations and solutions often change from day-to-day, it's
  important to have a record of how the client is supposed to behave
  -- a kind of functional spec.

* Karl, unfortunately, has been out of commission for 2 months,
  working on other non-Subversion things. However, as you may have
  noticed, he's recently got back on Subversion full time. He's now
  working (with Brane, hopefully) on implementing deltified storage in
  the repository filesystem. (The filesystem certainly works right
  now, but it's hard to take seriously without this feature.)

* Greg Stein has rewritten our build system and has been hammering out
  little buglets. He's also started changing some of our datatypes,
  so as to make SWIG bindings cleaner.

* Mike Sussman has started writing python tests.

In general, we're all working towards Milestone 3. This is the
milestone where we check Subversion into itself. If you want to see
what's required for M3, take a look in our tree at
`notes/alpha_short'. (This list also talks about what's needed for a
feature-complet Alpha and 1.0 release.)

Here's a quick summary of TODO items for M3:

   * working copy improvements: work with versioned directory use cases
   * user-props supported by ra_dav
      * autodetection of text/binary types, keyword subst, newline xlation
   * libsvn_repos
      * add cross-process locking function
      * add simple hook system
   * filesystem deltified storage
   * 'svn cleanup' subcommand
   * simple Apache authorization system
   * cvs2svn repository converter (needs SWIG->python->libsvn_fs bindings)

The good news is that everything is trucking along smoothly. The bad
news is that as usual, everything always takes longer than expected.
You've probably noticed that we're still pushing dates back on our
weekly status page. This is nothing to panic about, it's just that
every few weeks we stop kidding ourselves, do a reality check, and
adjust our schedule appopriately. (Things *have* been moving slower
without Karl!)

That's the news.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:31 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.