[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: patch manager

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Thu, 05 May 2016 23:05:47 -0500

Ivan Zhakov <ivan_at_visualsvn.com> writes:
>On 26 April 2016 at 10:58, Stefan Sperling <stsp_at_apache.org> wrote:
>> Hi Karl,
>> On IRC, you asked:
>> <kfogel> stsp: Is there anyone still in Patch Manager role in the project?
>> I just saw this, http://jk.ozlabs.org/projects/patchwork/, and thought it
>> might be helpful.
>> * kfogel asks the above question of Bert, Arfrever, or anyone else who
>> might know the answer
>> I don't think we've got an active patch manager at the moment.
>> We don't get many patch submissions these days, so there's not a lot to
>> keep track of. However, we don't have anyone working on Subversion full-time
>> either, so perhaps it's more likely now that patch submissions may end up
>> being ignored.
>> I like the idea, but at the moment I don't have time to make it happen.
>> We could try delegating the installation process to infra, but we'd need
>> someone at our end taking care of our patchwork instance beyond that.
>Why not just use JIRA to store patches? We used this in the past and I
>don't remember serious problems with this approach.

Sure, if that works, that's fine too. I didn't post on svn-dev@ about the 'patchwork' tool, which I hadn't heard of before now, because I wasn't sure the idea was valuable enough to be worth the dev list's attention. But it did pass my IRC worthiness threshold, so I mentioned it there :-).

Best regards,
Received on 2016-05-06 06:05:56 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.