Contributors mailing list archives


Re: Migration to version 9

Guewen Baconnier
- 31/08/2015 07:50:18

I won't speak about the one module/repo here because I think we don't
have the resources to achieve it even though I would love it.

On the 3 proposed solutions (filter-branch, rm, installable: False),
my voice goes certainly to the "installable: False" solution. It is
KISS and supports well the different git workflows (forward ports
merges...). Also, a script as proposed by Stéphane alleviates the
issue raised by someone which is that they don't know which module is
migrated or not.

Another thing which has not been evoked yet and has a huge importance:
the ill-display of the diff is one of the reason for which we take out
from the __unported__ solution. The "installable: False" solution is
the only one which correctly displays only the diff of what has been
changed for migrating a module. The other solutions would display the
entire module in the diff as additions.

Guewen Baconnier
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne
Phone: +41 21 619 10 39
Office: +41 21 619 10 10

On Sun, Aug 30, 2015 at 2:53 PM,  <> wrote:
> On Sun, Aug 30, 2015 at 2:23 PM, <> wrote:
>> It looks very good! I think we should include it as part of the
>> travis_after_success script independently from the final method used for v9.
>> We can have a that serves as base for the rest of the text.
>> Translation status seems to me now far down, but it's a detail.
> Agreed.
> I made a MQT PR with the script.
> -sbi
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe: