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

[Alexandre GOUAILLARD]

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
>