More frequent releases for enhancement/bug fix? #1887
Replies: 4 comments
-
|
The reason for the "slow" release cadence is mostly historical I believe, since fo-dicom used to be a lot more inactive. (And compared to other open source projects, it probably still is very inactive). Furthermore, the "keys to the castle" are currently in the sole hands of @gofal, who is the only one that is able to publish to nuget. Since @gofal has been absent here for a while now, I understand this might be annoying for you to wait so long for another release. I personally use a forked fo-dicom as a git submodule, which allows me to make changes in my fork and use them directly, while retaining the ability to merge upstream changes back into my fork. It also simplified stepping into the code while debugging. As for the packaging, I think @gofal uses Setup/0_BuildAndPack5.cmd, but I'm not sure whether it's up to date... |
Beta Was this translation helpful? Give feedback.
-
|
It probably makes sense to add instructions how to create a local package somewhere (Wiki or documentation), this should not be too much. |
Beta Was this translation helpful? Give feedback.
-
|
The instructions should be very helpful. :) |
Beta Was this translation helpful? Give feedback.
-
|
It seems the question has been already replied with an explanation about the release cadence. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What is, according to you, missing from fo-dicom? Please describe.
Context:
It's regarding issue JsonDicomConverter allows serializing DS/IS dicom item with invalid values, which should be fixed by PR #1354 soon. But seems next release of fo-dicom would not be very soon based on release history, which mean we won't benefit from the fix until next release. I'm wondering if there is any way to solve it.
Describe the solution you'd like
I have 2 proposals in mind.
I personally prefer the 2nd one, but I have no idea about how fo-dicom is published. So if there is any guideline for that, would be very helpful!
Describe possible alternatives or existing workarounds you've considered
N/A
Beta Was this translation helpful? Give feedback.
All reactions