[Insight-developers] Should we use a Gerrit or a non-Gerrit branch for mid-term dev?

[Marcus D. Hanwell]

Hi,

I am not sure why you can't integrate the pieces in as they are ready.
If it is desirable then an extra branch for long term development of
this work could be set up, and review performed there. So instead of
refs/for/master it would be refs/for/your-branch and topic branches
can start from there, and be merged back into there.

Once the long lived topic is ready, the whole thing could be merged.
Gerrit can have as many branches as we wish, but this sounds like a
question for Luis in terms of how he wishes to handle such a large,
long lived topic branch. It would be a shame to sidestep any kind of
review, as it is unlikely to happen at the end when you wish to merge
20,000+ lines of changes in (made up number).

Marcus

On Mon, Nov 1, 2010 at 9:30 PM, Alexandre GOUAILLARD
<agouaillard at gmail.com> wrote:
> Hi,
>
> I think gerrit is not the good tool for maturation of (large) code base.
>
> I would recommend to have a branch somewhere (github?) and to push to
> gerrit only when you think it's polished enough to actually make its
> way in ITK.
>
> alex.
>
> On Tue, Nov 2, 2010 at 5:27 AM, Michael Stauffer (Circular Logic)
> <mstauff at verizon.net> wrote:
>> Hi,
>>
>> We're preparing to add some significant changes to the registration code
>> for ITK 4.
>>
>> Should we create a separate main topic branch outside of Gerrit to use
>> and branch from while we work things out in the coming months, and then
>> only push the changes to Gerrit when they're ready? Can that separate
>> branch be within the main ITK 4 repo for easier pulling of changes to
>> master?
>>
>> Or do we have to go through Gerrit or create our own parallel repo until
>> we're ready to starting merging?
>>
>> Cheers,
>> Michael
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.html
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>