I thought I'd try to give at least weekly updates to keep everyone
informed of the progress towards the first 1.5 release candidate. I
know not everyone is able to follow what is going on 24/7 so figured
it would be helpful for keeping everyone in the loop.
It was a pretty good week last week, if we keep this up we should be
able to meet our October 12th goal.
There were 9 issues with the 1.5 milestone closed last week. There
was also a lot of other activity last week that was not related to
issues in the tracker. Everyone was very busy. I'll try to give some
highlights. I apologize if I leave anyone out. If you take a look at
how much has been done in the last week you will see it is easy to
Dan closed out the WC to WC copy issue (2822). That was significant
because it has been occupying a lot of his time, and driving him nuts,
over the last several weeks. So hopefully that will free him up to
tackle some other tasks in the list.
Paul finished off the various tasks related to non-inheritable merge
info and has taken on issue 2818 which is about providing an API for
merging arbitrary revision ranges.
Kamesh is still working on the new merge algorithm (2821) proposed by
Peter Lundblad earlier this year. He has found a few unrelated bugs
in merge that have sidetracked him while they are fixed. It looks
like the last of those was just committed though (r26499).
Karl seems to have a good handle on the sparse-directories work and
closed off several issues last week. It looks like Vlad continues to
help finish up this feature as well.
Lieven and Ivan have been resolving issues related to ra_serf. It
looks like Buildbot is down to 3 failures. I believe they have been
removing abort()'s in the process.
Erik continues to refactor and optimize the WC code. It looks like he
also resolved a couple of other issues from the tracker.
Hyrum is still improving the new log/blame -g options. He improved
the code for fetching merged revisions to make it streamy like the
rest of log. And he also modified the blame -g output to indicate
lines that were the result of a merge.
CMike also fixed a few issues and has started to look at some of the
new merge-related audit API's we need (2820).
Ben merged his copy-on-update branch to trunk. I am still trying to
sort out what that means exactly. It looks like right now he put some
code in place that will allow us to now work on making update smarter.
In other words, right now, things work the same but there are some
new API's available to be used that will be needed in doing this.
If you have been following the mailing list, the svn patch branch is
also getting ready to merge to trunk.
There are still 31 open issues with the 1.5 milestone. That includes
a couple of "umbrella issues".
The "big ones" in terms of new features are all related to merge
tracking with the new merge algorithm Kamesh is working on probably
Issue 2875 is about adding an option to svnadmin load to have it
create mergeinfo as part of doing copies. That seems like a big one
(effort-wise) and seems like it would be nice for helping people
Issue 695 about making svn checkout -N work would be a nice one to
close. Obviously the sparse directories feature is addressing this
issue. The last time I tried to test it to see if I could close it
there were still some problems though. I might just try again with a
There are some seemingly easy tasks out there for someone that wants
to just help us make progress:
2859: svn status --xml broken if user has changelists
2880: commit --changelist NO_SUCH_CHANGELIST should error
Dan reported an issue on IRC that it looks like he did not enter. He
could not commit a changelist because a file not in the changelist had
conflicts. Do we allow you to commit a named file if some other file
has conflicts? I assume so.
One we might need to push to a new release if no one steps forward:
2238: svn propset/del/edit does not support URL argument
Finally issue 2800 is about reconsidering our library renaming for
neon. It seems like we should come to some closure on this issue
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Sep 9 22:49:24 2007