Skip to content
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

[Dicussion] How much backwards compatibility do we support? #3662

Open
paulheinr opened this issue Jan 13, 2025 · 0 comments
Open

[Dicussion] How much backwards compatibility do we support? #3662

paulheinr opened this issue Jan 13, 2025 · 0 comments

Comments

@paulheinr
Copy link
Contributor

paulheinr commented Jan 13, 2025

Kai brought this up in MATSim advanced. One of the main reasons, why scientific (open source) software is able to compete with commercial software is that it doesn't have the business constraints like having a big support infrastructure (like high documentation coverage -- "code is documentation" -- or long backwards compatibility).

There are some questions regarding this topic (tbc):

  • Which parts of the code are so important that we maintain backwards compatibility?
    • e.g. external (input files like config, plans, network) vs. internal API (public/private guice modules)
  • Isn't backwards compatibility also for us a nice and important (?) feature? Code from older projects might break much earlier.
  • Are there explicit examples where backwards compatibility make the code worse and our life harder while maintaining?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant