Contributors mailing list archives


Re: Migration to version 9

Open Source Integrators, Maxime Chambreuil
- 27/08/2015 18:13:13
Before sprinting on anything, can we get back to the original subject and list all the options available on the wiki page ?

The problem we try to solve here is to optimize the effort of modules migration while keeping visibility and traceability. The use of unported directory showed his limit as people just moved the module one directory up.

If you want to share an option, please create a page and explain the procedure in 2 parts (branch creation and module migration).

Maxime Chambreuil
+1 (514) 276-5468 #126

----- Le 27 Aoû 15, à 12:52, <> a écrit :

Is there people then interested in make a code sprint for this?


2015-08-27 16:52 GMT+02:00 Guewen Baconnier <>:

On Thu, Aug 27, 2015 at 4:37 PM, Alexandre Fayolle
<> wrote:
> I quite like the suggestion of having information about the ported
> addons in the We could list the unported / uninstallable
> addons in a separate section.
> And we could use the opportunity to add a short paragraph describing
> what the addon does (using the summary from the manifest?). This is
> something we can provide a script for in maintainer tools.
> Alexandre
> On 27/08/2015 16:23, Guewen Baconnier wrote:
>> Setting aside the separate repos discussion, my biggest concerns are
>> the corruption of the history that would be inflicted by the git
>> filter-branch on renamed modules and the forward-port of merges.
>> Renaming a module is not an uncommon scenario and the forward-port is
>> something we really use.
>> If we can find a solution for these problems, I think I could do with
>> this procedure. Otherwise I would prefer the simple method of just
>> setting 'installable' to False.

Post to:

Post to: