-
Notifications
You must be signed in to change notification settings - Fork 7
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
Different branches #7
Comments
There was no real reason to branch till now and nobody ever questioned it. I see a basic pro/cons situation: If we branch we have to push the changes to multiple branches everytime. (e.g. update the CI, documentation of a new feature). dob can work down to Odoo version 8 (replace doblib with doblib-legacy in the dependencies if you want to go below 11.0). If we keep everything in one branch you might have to adjust the Our current premise is:
|
Ok, I understand your point. What about tagging the latest commit where dob was based on the previous Odoo version. |
We have documented the features in the docs folder but the features are implemented within the python package Maybe we can think about storing some patches within the repo to get to the different versions more easily. Not sure how we would handle the versions of the python packages. |
Ok thank you for your response. Anyway, it would be great if we could get a previous version of Odoo in a quick way. But doesn't matter. If you have got a suitable solution, feel free to make a short update here. Thank you for developing dob an making it Open Source. |
What is about placing different Dockerfiles in the repo:
|
Hello,
I would be interested why dob is not separated in different branches for various Odoo versions.
Thank you for the information.
The text was updated successfully, but these errors were encountered: