On Mon, Feb 21, 2011 at 09:54:12PM -0800, Rick Varney wrote:
> Hello,
>
> I am introducing Subversion into our development environment. We are using a
> lock-modify-unlock stategy for all of our files. I do not claim this is the
> best or most efficient way to use Subversion, but it best fits the mindset of
> the developers at my particular site. We have installsed Subversion 1.6.6.
>
> We ran into the bug documented as issue 3471: "svn up touches file w/ lock &
> svn:keywords property"
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3471
>
> This is an annoyance for us, as we are using make to do our builds.
>
> I am new to the subversion community, though I have had my eye on it for a long
> time. Here are my questions:
>
> 1. Is there a way for me to find out if there is planned fix for this issue?
No, apart from asking here or on dev@.
You can never exactly know who is working on what in an open source
project because resources aren't being managed from a central point.
That said, I'm not aware of anybody having expressed interest in
working on this issue. But I don't know everything the community
is up to, either.
> 2. If there is not a plan to fix this issue in an upcoming release, is there a
> way I can find out if anyone else has submitted a fix?
Related patches will usually be logged to the issue.
Unless a patch has been submitted without people realising that there's
an issue filed for the problem. So again, you can never be sure :)
Searching the archives is the most reliable source of information about
past contributions. The archive at http://svn.haxx.se/dev has a search box.
> 3. If there there is no submitted fix, how would I go about submitting one
> should I attempt a fix myself?
This should get you started:
http://subversion.apache.org/contributing.html
In particular note these two sections:
http://subversion.apache.org/docs/community-guide/general.html#code-to-read
http://subversion.apache.org/docs/community-guide/general.html#patches
I found those two very valuable when I started out contributing to Subversion.
> 4. If I were to attempt a fix, I would likely not be able to spend a great deal
> of time fully verifying it, given that this is outside of my usual job
> responsibilities. Is there a way to submit a fix that others could help verify
> - assuming that there are benevolent souls in the community that do this sort of
> thing?
Yes, sure. We do encourage new contributors and try to help them
off the ground as much as possible. Sending a patch to dev@ will
usually trigger feedback right away. If it doesn't you can re-send
every couple of days letting people know that you haven't received any
feedback yet. We never ignore contributions on purpose. We have a patch
manager who takes care of contributions that have slipped through the
cracks in case submitters don't ping their own contributions:
http://subversion.apache.org/docs/community-guide/roles.html#patch-manager
> In short, please clue me in on the conventions of getting or making a fix to a
> bug I care about. I am fine if the answer is "Read The Fine Manual", but do
> please point me right manuals.
>
> Many thanks in advance!
Hope this helps!
Stefan
>
> Best regards,
>
> Rick Varney
Received on 2011-02-22 10:28:08 CET