On 7/16/07, Daniel Rall <firstname.lastname@example.org> wrote:
> > >There's one thing I want to add: we also have another source of TODO
> > >items and that's the list of XFail-ing tests in the test suite. Not only
> > >do they indicate certain issues or missing features, the fact that
> > >someone took the time to write those tests shows a genuine interest in
> > >getting the issue fixed or the feature implemented.
> > >I want to propose - as a best practice, not as a strict project
> > >requirement - that we add tests or placeholders for those features or
> > >issues we want to get fixed in 1.5 and include a reference to those
> > >tests in the issue description. I know we already have them for the
> > >'--depth' feature, it'd good to know which of them Karl considers as
> > >mandatory for 1.5 release.
> > It seems like XFAIL's that are going to live in the code for more than
> > a few weeks ought to have an issue associated with them right in the
> > text description. That would make it easy to have an extended
> > discussion around the test and see when it is planned to be fixed, or
> > what is blocking it.
> Good idea! How about adding it as a guideline to hacking.html?
Lieven, did you want to take a crack at this? I think you could say
it much better than me.
> The remaining loose ends for 1.5.0 still need to be enumerated, and
> tossed into the issue tracker (even if only at a very coarse
> granularity). Here's a starting point -- just a strawman -- for the
> list of remaining loose ends:
> - 1.4.x/1.5 client/server incompatibilities. (Reported by glasser in
> - Sparse directories/--depth option
> - See the "Current Status" section of notes/sparse-directories.txt.
> - Review "TODO(sd)" comments in the code.
> - ra_serf/ra_neon
> - Progress callback busted between May 16 and June 21. (Reported by
> Dan C. from Google in
> - Outstanding SVN DAV library config issues?
> - ra_serf-specific
> - Remaining abort()'s?
> - (What else...?)
> - XFailing tests
> - (Which in particular absolutely need to be resolved...?)
> - Changes needed by Subclipse...?
> - Changes needed by TortoiseSVN...?
> - Language bindings updates for API changes...?
- fsfs transaction name problem
- DAV write-through proxy feature. Someone posted a question on
users@ without a reply:
I still wonder if it could be made to work cleaner, such as use
svnsync without any hooks.
- svnmerge conversion script? I think this has been talked about but
I do not know who plans to do it.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jul 17 01:46:15 2007