-
-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ONESTEiN Contribution #84
Comments
Hi, Glad to see that you're interested by this project. Yes, the wiki is not very up to date. Com' on guys, plz update the list with the current state! (@arthru, ccomb, c2c, @StefanRijnhart, ...) Do you have some questions about how OpenUpgrade works, or how to contribute ? About the list of your module you want to cover, the most important work is in 'stock & co' for the 7.0 -> 8.0 migration. Plz, see this post #82 and contact Alexandre if you want more information about the changes. Regards. |
Thank you, about OpenUpgrade we know how to use it. We started migrating some small modules and we felt quite comfortable with the process. About the contribution, as ONESTEiN we are now starting to be involved in the effective contribution to the Odoo ecosystem; for now we forked the OpenUpgrade project and we are going to take it as a basis to start working on the missing modules; so we will make our pull-requests to merge the code in the 'official' OpenUpgrade from our fork. For all the information related to the progress and the technical discussions we will refer directly to the pages of the main project. Do you think that might be a good way to work? Regards, |
Hi, I updated the 'planned migrations' wikipage with the modules that we are going to migrate by september 2014. @legalsylvain: I saw that for some of these you had already planned the migration for 2015 ... I reinserted them in the table assigned to us but, if you want to collaborate, we would be glad to work with you in the implementation of the scripts. Regards. |
@diellenne Will you have a public branch of your efforts? I would really like to cooperate with |
@plaes I'm glad that you want to cooperate with us to improve OpenUpgrade faster. We landed on GitHub as onseteinbv just from a little so we are trying to organize our repositories in the best way to share our work. Gr, |
I've yet to figure out the way to get the analyze part running successfully, failing in the And my current migration efforts fail with following error:
|
@plaes It seems the problem lies with the function that sets the default for location_id. As a temporary work-around you could set the value in the _defaults dict for location_id in stock_inventory to False. |
OK, after a somewhat long hiatus, I got some work done in my https://github.com/plaes/OpenUpgrade/commits/wip-mrp branch which is based on onestein's stock migration branch. It will be rebased and I'll probably amend the 'Various hacks...' commit when need arises. |
Hi @plaes , @pankk has completed your work on 'mrp' on our fork (https://github.com/onesteinbv/OpenUpgrade) in the brach os-dev. |
Yup, I saw that.. How do you guys handle the broken xml stuff (views, model and field data) which is stored in the database? This part is still real magic for me, though I tried to write a small script (pull #91) to detect some of the discrepancies. |
@plaes This differs; in depth functional knowledge is required to see what should be done with the data. |
Hello, my name is Ronald Rubí and I am team manager in ClearCorp (Costa Rica). |
Hi, Ronald, you can check current PRs (pull requests) - https://github.com/OpenUpgrade/OpenUpgrade/pulls - to review them, or create a new one with the migration scripts you have done. Currently, there is a proposition for stock module migration here: #125. |
Thanks, Pedro! |
Hi everybody! Cheers! |
Thanks, Diego. Any help will be welcome. Regards. |
Currently working on review and test. I'm closing this chit chat now ;-) |
In order to accelerate the development and increase the coverage of OpenUpgrade v8 in the next few days our team will start to contribute to the project: in particular, we would like to complete as soon as possible the following modules:
Concerning the modules that are already in progress, we would like to hear from everyone who is actually working on these in order to share the missing work; for the others I will update the wikipage with our planning as soon as possible.
The text was updated successfully, but these errors were encountered: