Comments (2)
If we are strictly observing Semantic Versioning then I can see that the numbering 1.2.1 -> 1.2.2 is not correct, however:
- the classes removed were only used internally for visualisation. Technically they should have been marked protected (hence could have been removed without changing any public interfaces) but I don't believe they were.
- the classes removed were not compatible with the Modelica Language Specification, and therefore ensured that the library would not function in any tool other than Dymola. Maintaining such a status until a "later release" is not feasible for commercial use of a library.
- the library was checked in Dymola to ensure behaviour had not changed. Since Dymola was the only tool that would be affected by backwards-compatibility, since other tools could not support the library, this seems a sufficient test.
from vehicleinterfaces.
I agree fully with point 2 and understand 3. In contrast, the internal usage of the classes is only an assumption.
But maybe this bother only myself because I have used that classes for my visualization classes (already modified them).
from vehicleinterfaces.
Related Issues (20)
- I have a question. HOT 6
- Add milestones and labels HOT 1
- Replace "fake" enumerations with enumerations in VehicleInterfaces.Types HOT 2
- Error in VehicleInterfaces.Mechanics.NormalisedTranslational.Interfaces.Flange documentation
- Remove uses of __Dymola_choicesFromPackage annotation HOT 2
- Reintroduce the idea of expandable connectors for signal buses HOT 10
- Incorporate FlangeWithBearingAdaptor in models with FlangeWithBearing HOT 1
- Restructure examples in Roads HOT 1
- VehicleInterfaces.Drivers.MinimalDriver cannot be instantiated HOT 8
- Load torque parameter description misleading HOT 1
- MultiBodyEnd purpose HOT 2
- Relicense under BSD 3-clause? HOT 5
- Split library into single files
- Rename includeAccessoriesBearing
- Delete obsolete classes
- Change Greek parameter name 'mue' to 'mu'
- UsersGuide.DriverInteractionBus have misleading engineSpeed and vehicleSpeed descriptions HOT 1
- Hide usingMultiBodyXXX when the corresponding includeXXXBearing is set to true HOT 2
- Layout of road functions in Roads.Interfaces.Base HOT 2
- Units error (or incompatibiity?) in VehicleInterfaces\Engines\MinimalEngine.mo: r/min vs 1/min HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vehicleinterfaces.