[vtk-developers] gerrit bug fix backports

[Marcus D. Hanwell]

We could add a VTK 5.10 branch to Gerrit (or whatever name we wanted
to use), and push topics for review there with merges and mirroring
similar to master. Gerrit would have no problem maintaining two
branches, we probably need to improve the CDash at Home scripts to allow
it to use different source/binary directories for the two branches
(otherwise confusion/long rebuilds would result). With the large
changes between 5 and 6 I certainly see value in at least maintaining
a branch where backported bug fixes could go.

Marcus

On Tue, Sep 3, 2013 at 11:40 AM, David Gobbi <david.gobbi at gmail.com> wrote:
> When VTK 4 became VTK 5 this was not an issue for me because I had
> access to the VTK 4 branch and continued to push bug fixes to it for a
> year or so.
>
> But now, there is no VTK 5 branch, and submitting VTK 5 patches to
> gerrit is a no-go.  I'm not complaining about gerrit, I love it, but right
> now it is not set up to handle patches against old releases.
>
>  David
>
> On Tue, Sep 3, 2013 at 9:19 AM, Berk Geveci <berk.geveci at kitware.com> wrote:
>> This is a good discussion. I'd like to see what people think. In the past,
>> we haven't put a lot effort into maintaining two versions but given the
>> larger change between 5 and 6, it might be justified to spend some cycles
>> maintaining 5 for a while. I'd like to hear what people think about how long
>> and how.
>>
>> -berk
>>
>>
>> On Tue, Sep 3, 2013 at 10:48 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>>>
>>> On Tue, Sep 3, 2013 at 8:23 AM, Dean Inglis <inglis.dl at gmail.com> wrote:
>>> > A software project I am working on is being developed with the vtk
>>> > 5.10.1
>>> > release branch. 3 bugs in that branch reported by our group were
>>> > addressed
>>> > using gerrit (Iccc5a316, I561346c4, Ifbea52c2).
>>> > We are currently using customized copies of the involved classes
>>> > in our code but would like to use the original (fixed) vtk classes.  Is
>>> > there a process
>>> > for backporting bug fixes to previous releases?  What is Kitware's
>>> > policy on
>>> > bug fix backports to existing release branches?
>>>
>>> I'm curious about this, too.  Right now all of my apps are still based
>>> on VTK 5 and I don't intend to move them over to VTK 6 until around
>>> VTK 6.2 or so.  I have a few local patches for VTK 5, all backports of
>>> bug fixes, but right now there is nowhere for them to go.
>>>
>>>  David
>>> _______________________________________________
>>> Powered by 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
>
> 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
>