[vtk-developers] Patch integration frequency

[TINGAUD Frederic]

No problem Sebastien!
As I said, I am not complaining about the time it takes. Most of my patches received comments in the hour following my push, which pointed real problems in my implementation and I am conscious that these patches are not the only thing you are working on.

-----Message d'origine-----
De : Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] 
Envoyé : mercredi 24 octobre 2012 19:55
À : TINGAUD Frederic
Cc : David E DeMarle; vtk-developers at vtk.org
Objet : Re: [vtk-developers] Patch integration frequency

Hi Frederic,

I did not forget about your patch and I'll do my best to get to it but that piece of code can be tricky, so I truly want to take the time to validate it instead of just approving it without really looking at it.

Seb

On Wed, Oct 24, 2012 at 1:42 PM, TINGAUD Frederic <Frederic.TINGAUD at murex.com> wrote:
> Thanks for your answer David!
> I did more than just checkout git master, I have two patch branches 
> waiting for integration on it (one bug correction #1470 and one feature #1438) :) The goal of my question is to be able to decide whether I package my application with a custom VTK version containing my patches or if I can wait for an official release integrating them or third solution, a night build that contain them.
>
> Regards,
>
> Frederic
>
> -----Message d'origine-----
> De : David E DeMarle [mailto:dave.demarle at kitware.com] Envoyé : 
> mercredi 24 octobre 2012 19:28 À : TINGAUD Frederic Cc : 
> vtk-developers at vtk.org Objet : Re: [vtk-developers] Patch integration 
> frequency
>
> On Wed, Oct 24, 2012 at 12:02 PM, TINGAUD Frederic <Frederic.TINGAUD at murex.com> wrote:
>> Hi all,
>>
>>
>>
>> As I am still quite new to the list, I don't yet have a vision of VTK 
>> evolution frequency.
>>
>> I see that a 5.10.1 has been released a few days ago. How often does 
>> this kind of minor release happen?
>
> VTK releases have no particular schedule. We aim for a new release a couple of times a year, and typically alternate minor (major.minor.0) and patch releases (major.minor.patch). We rarely do more than one patch release per minor release.
>
>> Is it the only moment were patch branches are merged into the master 
>> branch or are they merged continuously and the tag just freezes the 
>> state of the master at a given point?
>
> The master branch continuously changes as we add new code.
>
> We make major/minor releases by picking some good point on the master branch to start a new release branch from. Once the  release branch is tested enough we tag it and update the downloads page.
>
> Afterward the release branch grows only when we do a patch release.
> These consists of just important bug fixes. New features go in via the master branch only.
>
>>
>> Do we have a vague idea about the ETA of next major release?
>
> 6.0.0 will be ready about January when a handful of remaining features go in and when the regression test dashboards get cleaned up. You should try it by checking out the master branch from git.
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
> *******************************
>
> This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.
>
> _______________________________________________
> 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
>
*******************************

This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.