>> sorry for the probably unrelated question, but why isn't true rename
>> on the list of features for 1.5/1.6?
>Because it is a *lot* of *hard* work? Because people want
>merge-tracking more? Because people wanted sparse-directories too?
>Because ... (well, many reasons)
>> Is it being worked on at all?
>> Aplogies in case I'm wrong or I've overlook something and thanks in
>> for the info.
>You're not wrong, but you are sounding demanding. What did *you* do to
>make sure rename support is in it?
I do not want to start a fight here and since I haven't been actively
involved in subversion mailing list I cannot be too *demanding* either.
However, as one big supporter of true renames, I have several times
lobbied to have this addressed. I did it back in 1.0, after 1.2 and now.
I remember exchanging a few emails with Karl and expressing my view on
the mailing list. Given this issue lasted 5 years I am sure these
comments were lost. So understand that I am DEEPLY disappointed by 898
been postponed for the 6th time.
So my question is: how as the subversion development team, have you
facilitated the gathering of feedback from your user base and made sure
it wasn't lost?
As a user, how do I make sure my voice is heard at the right time? How
do I know when it is time to lobby again for a feature?
Remember, we have daily life too and keeping track of subversion user or
dev mailing list may be too much to ask (it was for me for the past 1+
I could not find anything on the web site about a feedback process.
I believe that without a well defined process to define a release scope,
it is very hard to get a good idea of your user base needs.
I suggest you spell out the process and ensure it is simple: some like
vote on the issue you care about or send an email explicitly to ask
feedback on content of next release or publish a wiki document and let
people comment on it...
FYI at some point the voting system of collabnet issue tracking was
available and I invited several co-workers to vote for that issue. I
suppose it was turned off because you were not using it. Did you have
reason to reject its information?
Again, even though I am passionate about this issue, I am also a
passionate supporter of subversion. So thanks for producing such a great
tool and investing your [personal] time into it.
My life as a [open-source and closed-source] developer has been made
significantly less painful since we started using subversion (since 1.0
in some projects).
Received on Thu Apr 12 21:39:49 2007