You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@red-bean.com> on 2016/05/06 04:05:47 UTC

Re: patch manager

Ivan Zhakov <iv...@visualsvn.com> writes:
>On 26 April 2016 at 10:58, Stefan Sperling <st...@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,
-Karl