I've not heard any objections to the proposal to start driving towards a
1.1 release. So I'm taking the wheel.
What I'm doing today is trying to narrow down our definition of 1.1.
This means a whole lot of reorganization of the issue tracker. Please
bear with me, apologies for all the forthcoming email.
What I'm doing is this:
* pushing all 1.1 issues into 1.2.
* moving things that I think are critical back into 1.1.
* moving things that I think require debate (*might* go into 1.1) into
a new milestone called "1.1-consider".
So my request, in case you're new to this community, is: please, don't
start appending rebuttals to these issues when I reorganize them. Let's
save our debates for this list. :-)
Here's my current roadmap, in case you're wondering what I'm trying to
sculpt the issuetracker into. Obviously, this will morph a bit as we
discuss things.
New Features
------------
fsfs --> (catmagic says we still have win32 probs?)
l10n
diff follows rename --> requires speedup (1846)
Features under Consideration
----------------------------
IRI->URI conversion (1910)
version checks/API (1763, 1861)
user-defined keywords (890)
Outstanding critical bugs
-------------------------
hotcopy bugs (1817, 1818, 1819)
win32 large diff failure (1789)
win32 mysterious svnserve failure (1863)
win32 mysterious file-not-found (1862)
Critical bugs under consideration
---------------------------------
disable co/up -N (?)
lingering win32 case-sensitivity bugs (1495? others?)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 8 19:20:32 2004