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

Make a general plan for python and java release support #174

Open
sanjayankur31 opened this issue Oct 11, 2021 · 0 comments
Open

Make a general plan for python and java release support #174

sanjayankur31 opened this issue Oct 11, 2021 · 0 comments
Assignees
Labels
C: NeuroML software C: NeuroML software Type: Strategic Type: strategic

Comments

@sanjayankur31
Copy link
Member

In general, for both Python and Java releases, we should make a plan that says "after a release reaches EOL, we support it for another XYZ months before we drop support".

This is necessary so that in the future, we're able to drop support for EOL core tech in good time. For example, Python 3.6 will be EOL in December 2021, so some time after, we should drop support for it.

This also reduces our maintenance burden since keeping EOL versions functioning is quite a bit of work now, especially if there are major changes.

What we come up with needs to be clearly documented in docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: NeuroML software C: NeuroML software Type: Strategic Type: strategic
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants