-
Notifications
You must be signed in to change notification settings - Fork 126
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
Feature/tp/add polyline model #484 #688
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
force a rebuild of protobuf Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Philip Windecker <philip.windecker@avenyr.de> Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
82d6daf
to
91120e6
Compare
This PR has commits regarding the build pipeline which would need to be removed. Als #666 had some changes regarding Antora? |
@ThomasSchloemicherAVL : Is this change still a requirement and needed? |
@ThomasNaderBMW yes please. @jdsika yes sorry, that was my mistake after a rebase. |
@ThomasSchloemicherAVL: Would you like to join the OSI Other Models Working Group (22nd of May; 9-10am) to present and discuss the intention and further proceeding for this PR in the group? Some weeks ago we still had some open questions/concerns but it could be merged for OSI 3.6 after some adaptions. Also, the build pipeline stuff should get fixed at some point. |
@thomassedlmayer sorry for the late reply. Yes, please add me to that meeting.. |
Is this still a valid PR? If yes, should it be included in v.3.7.0? |
OSI 3.7.0 is closed for new features. |
Reference to a related issue in the repository
Add a reference to a related issue in the repository.
Add a description
Add a description of the changes proposed in the pull request.
Some questions to ask:
What is this change?
What does it fix?
Is this a bug fix or a feature? Does it break any existing functionality or force me to update to a new version?
How has it been tested?
Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:
If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!