1. Mailing Lists
  2. Contributors
  3. Re: Confusion about branch 9.0 in github

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Confusion about branch 9.0 in github

Re: Confusion about branch 9.0 in github

Avatar

Re: Confusion about branch 9.0 in github

by
Elico Corp, Eric Caudal
- 13/11/2015 10:24:25
I am in favor to restart from clean repos (sorry for the hard work done).
With current situation today, there is confusion and it doesnot even bring the certainty that the history is sync'ed between version.

When we need to port for sure a module, the first day we apply a git magic to link the history between existing v8 and v9 (a fork will happen at that time but we do not care too much) and people might start working.

I am still not sure this is the way to go though. when starting the migration, the developer will clone in his repository the v8 branch, a lot of previous code might simply be scrapped locally and then a PR will be done with the result into the v9 branch. In this case I do no see the point even in transiting via the v9 repo to start the process.
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 11/13/2015 04:53 PM, Daniel Reis wrote:
<blockquote cite="mid:5645A404.7050408@sapo.pt" type="cite"> 
As a coincidence, yesterday I was doing some writing about v9 and came 
to the conclusion that it would be best to skip OCA 9.0 repos, since I 
found confusing to explain the existing yet disabled modules.

In fact fact in the previous discussion we had to weight a clean Git 
history versus clarity on the ported modules.
The final decision favoured Git history, and tried to minimized the 
visibility issue with a table with the unported modules.

With the current situation, usability comes second to an easier 
retrieval of the change history.
And the current solution still has the problem we found with the 
__unported__  directory:
if the 8.0 evolved in the meanwhile, people porting to 9.0 the diabled 
code in 9.0 will miss thos changes.
They will need to notice that and use some git hacks to get the missing 
changesets, but that's about the same work you need to git extract a 
module from 8.0 to 9.0 if 9.0 branches started out clean.

I do think it's not a waste of time to reevaluate these options now, so 
I welcome this discussion.
I stand on my position on that discussion, and still think that the best 
option is to delete de unported modules from the 9.0 branch.


Regards
Daniel

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference