-
Notifications
You must be signed in to change notification settings - Fork 6
Unclear what the latest version is #88
Comments
Hello @ximion ! You are completely right! We stopped tagging new releases when we decided to use mod2c exclusively as git submodule under BlueBrain/CoreNeuron and now neuronsimulator/nrn. Also, this (older) tool is not a general purpose but only meant to use internally by NEURON/CoreNEURON simulator. And that's when we stopped taking care of releases. (New alternative is https://github.com/BlueBrain/nmodl). We can make a new release if this is desirable / helpful for distributions. Could you just tell us a bit about where/how you are packaging this? (and based on above comments, do you think this stills need to be distributed independently?). |
Hi! In Debian anything that could be used by multiple projects needs to be in a separate package, as having multiple code copies in multiple places is a nightmare for both license review/compliance as well as fixing security issues (if there is a code copy in 300 places, a security issue needs to be addressed 300 times, while if there is one shared code copy, it only needs to be fixed once). It's a matter of keeping a software distribution maintainable for years without the task becoming too overwhelming. (see https://wiki.debian.org/UpstreamGuide#No_inclusion_of_third_party_code ) As for this particular package: If it's only used by NEURON, I think just merging the code into the Neuron repository is likely the easiest thing to do, then you don't even need to worry about separate releases or keeping a submodule up to date anymore. Otherwise at least making a release with a higher version number would be good - we can package Git snapshots of upstream projects, but if there are newer tags, it confuses a bunch of automation on our side that alerts about new upstream versions (which in turn confuses people looking at the messages ^^) |
Coincidentally, |
Completely agree! (in this specific case, we want to remove mod2c usage soon)
Ok. But just to be sure: if there is a newer tag, you want something that is compatible with the latest neuron release like 8.2.x, right? |
Yes, that would be nice! At the moment we're using a Git snapshot: https://tracker.debian.org/pkg/nrn-mod2c (which works as well). |
Hi!
The latest and most current tag and marked release for this project is version
0.9
from Oct 5, 2016, which previously on Aug 30, 2016 version1.2.0
was tagged.This is very confusing, especially for Linux distributions which package this tool.
Could it be clarified what the latest version is, either by renaming the 0.9 tag or by renaming the other tag, depending on what the intended version is? (easiest solution and probably the one with the least amount of chaos would likely be to just make a new release with a version number higher than
1.2.0
)Thank you! :-)
The text was updated successfully, but these errors were encountered: