[vtk-developers] New VTK merge master (need to merge something to VTK-5-4? -- please read this...)
Gerrick Bivins
gbivins at objectreservoir.com
Mon Apr 13 11:59:04 EDT 2009
Yes. That makes sense. It could be that my ³request to get patches
reviewed/committed² isn¹t appropriate. Is there a defined procedure to get a
commit privileged developer to review/commit community submitted patches?
Typically, I¹ll run across an issue that hasn¹t been reported before( or at
least I haven¹t been able to find a case on the boards or in Mantis). I¹ll
post a question to the users list to illicit a response from the community.
If there are no responses I¹ll attempt to fix it myself. If I come up with a
reasonable solution, I then post a patch to vtk-developers and also Mantis.
Is that about right?
How would I get the attention of a developer to initiate the new process?
I¹ve only seen the process defined for developers with commit privileges (
http://www.vtk.org/Wiki/VTK_cvs_commit_Guidelines) .
Gerrick
On 4/13/09 10:30 AM, "David Cole" <david.cole at kitware.com> wrote:
> First, somebody who does have commit privileges will have to apply your
> patches from Mantis to CVS HEAD of VTK and record the cvs logs of the
> activity... Then, the developer who does that can request (via adding a note
> to the mantis entry even...) for it to be merged to VTK-5-4 and follow the
> procedure outlined on the Wiki.
>
> Does that sound reasonable?
>
> Thx,
> David
>
> On Sun, Apr 12, 2009 at 11:43 PM, Gerrick Bivins <gbivins at objectreservoir.com>
> wrote:
>> How does this work for those of us who do not have commit privileges yet?
>> I¹ve submitted a couple of patches via Mantis previously (last month or so)
>> but they haven¹t made it through.
>> Gerrick
>>
>>
>>
>> On 4/10/09 2:35 PM, "David Cole" <david.cole at kitware.com
>> <http://david.cole@kitware.com> > wrote:
>>
>>> Hello VTK devs,
>>>
>>> Some of you may have noticed that the latest VTK release announcement email
>>> came from Zack Galbreath instead of me.
>>>
>>> Zack Galbreath of Kitware, Inc. has taken on the roles of VTK release guy
>>> and VTK merge master. In helping him transition to those roles, we have
>>> added a Wiki page describing how to submit a patch (from changes you make to
>>> VTK CVS HEAD) to be included in the next bug-fix-patch release of VTK.
>>>
>>> Please review the information on http://www.vtk.org/Wiki/VTK_Patch_Procedure
>>> <http://www.vtk.org/Wiki/VTK_Patch_Procedure> and follow it diligently when
>>> preparing patches to be merged to VTK-5-4 (and future release branches).
>>>
>>> Any questions? Post them here... I'm sure Zack will chime in.
>>>
>>>
>>> Cheers,
>>> David Cole
>>> Kitware, Inc.
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com>
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>
>>
>> _______________________________________________
>> Powered by www.kitware.com <http://www.kitware.com>
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20090413/8852f14e/attachment.html>
More information about the vtk-developers
mailing list