Recently, Greg Stein pointed out here that the CollabNet developers
cannot bring Subversion to 1.0 alone, an observation which I'm sure
shocked no one who follows the dev list and commit emails :-).
However, the CollabNet people have been mostly (though not entirely)
responsible for handling the "milestoned" issues, that is, stuff
scheduled in the issue tracker to be resolved by a certain date. It
would be *great* if more people want to get involved in those issues,
though -- they're generally the most critical either in terms of
severity, or in terms of the number of other issues they block.
Here, let me be more concrete. Can someone start this off by taking
http://subversion.tigris.org/issues/show_bug.cgi?id=872
...which is set for 0.16, the next milestone? :-)
That bug is one of the real showstoppers right now: Subversion doesn't
do i18n on Win32, because of some problems in the apr/apr-util i18n
support. I believe many of those problems have been at least
partially resolved since the issue was filed, but whoever takes this
on will still probably need familiarity with APR* as well as
Subversion. You'll get plenty of help from the dev list; there's
plenty of expertise here for APR as well as Subversion. Brane in
particular had some detailed thoughts on this issue <blatant hint/>.
By the way, on a more general topic:
CollabNet obviously doesn't have some exclusive right to decide what
issues go in what milestones :-). When we do it, it means we're
committing that the work will be done by that date, probably done by
us but not necessarily. However, anyone else is free to use that
criterion too -- if you schedule an issue, just please make sure the
work gets done according to that schedule (because people may plan
other dependent issues accordingly).
In practice, of course, it's probably good to have just one or two
people reviewing and scheduling issues in close consultation. There
are so many dependencies and relatednesses to watch out for, and of
course whoever does this on a regular basis gets familiar with all the
outstanding issues, which helps a lot. So far I've been doing that
job, and was planning to continue. But if you strongly disagree about
a prioritization, please post! I don't want to ride roughshod over
any other developers here, just trying to keep things focused and see
that the most important bugs get addressed, with the minimum overhead
possible.
Thanks,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 11 17:50:08 2002