Please make a versioned release

[yarikoptic]

Ideally following the semantic versioning https://semver.org .

[frankyeh]

Thank you for the suggestion. I wish I could do a versioned release, but currently TIPL is mainly developed for research purpose, and the update is continuous over time. It is challenge to have a version control under limited manpower. Sorry for the inconvenience.

Best regards, Frank

On Wed, Apr 10, 2019 at 4:27 PM Yaroslav Halchenko notifications@github.com wrote:

Ideally following the semantic versioning https://semver.org .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/frankyeh/TIPL/issues/7, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQ0cXKdu7WqygWWgAdkh63rdfsm3oW3ks5vfkkUgaJpZM4coL6k .

[yarikoptic]

may be @frankyeh of DSI-Studio could help maintain ? ;) my "greedy" desire here is to package DSI-Studio (and thus TIPL) for NeuroDebian as one of my collaborators wants to use it. Having SOME releases/versioning would be better than me just coming up with 0.0.DATE "release"

[frankyeh]

Sure. @frankyeh https://github.com/frankyeh of DSI-Studio would love to help :)

DSI Studio has very high turning rate as per feature request or bug fix proposed by users (e.g. it was just updated today to fix a minor issue for a user).

Currently we use "release date" as the version when communicating with users.

Hope this is a possible workaround for you.

On Wed, Apr 10, 2019 at 10:20 PM Yaroslav Halchenko < notifications@github.com> wrote:

may be @frankyeh https://github.com/frankyeh of DSI-Studio could help maintain ? ;) my "greedy" desire here is to package DSI-Studio (and thus TIPL) for NeuroDebian as one of my collaborators wants to use it. Having SOME releases/versioning would be better than me just coming up with 0.0.DATE "release"

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/frankyeh/TIPL/issues/7#issuecomment-481939538, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQ0cfxvjrKy7-h67LaXH6Ihicu_mzkNks5vfpwDgaJpZM4coL6k .

[yarikoptic]

FTR: I still don't see any tag or release being posted to https://github.com/frankyeh/TIPL/releases so not sure why this issue was closed

[frankyeh]

Sorry for closing this issue. The point in my last communication is that I cannot formally provide a versioned releases due to frequent updates in DSI Studio and TIPL. Instead, I usually communicate with users using the "date" of the TIPL their downloaded. I can re-open this issue again if needed. Frank

On Fri, Nov 8, 2019 at 11:28 AM Yaroslav Halchenko notifications@github.com wrote:

FTR: I still don't see any tag or release being posted to https://github.com/frankyeh/TIPL/releases so not sure why this issue was closed

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/frankyeh/TIPL/issues/7?email_source=notifications&email_token=AACDI4MNM4Y32RFX3G7ZDWDQSWHUHA5CNFSM4HFAX2SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDSUFCQ#issuecomment-551895690, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACDI4PRXBECWJDOT2MJQQDQSWHUHANCNFSM4HFAX2SA .

[yarikoptic]

up to you -- it is your project(s). just know that your users (and outsiders like me) would only appreciate additional effort of the mighty git tag (at least) or pressing a button on releases pages

[frankyeh]

Thanks for the suggestion. I will try it out. Best regards, Frank

On Sat, Nov 9, 2019 at 6:56 PM Yaroslav Halchenko notifications@github.com wrote:

up to you -- it is your project(s). just know that your users (and outsiders like me) would only appreciate additional effort of the mighty git tag (at least) or pressing a button on releases pages

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/frankyeh/TIPL/issues/7?email_source=notifications&email_token=AACDI4PZ5N7323H4RMQM7NTQS5E3LA5CNFSM4HFAX2SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDUR3SY#issuecomment-552148427, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACDI4LCHDONIFA7UG6WBK3QS5E3LANCNFSM4HFAX2SA .

[frankyeh]

I created a 2019 November release and will create new releases regularly in the future. I did not know this function previously (sounds ridiculous...but true) and thanks for the tip! Best, Frank

On Sat, Nov 9, 2019 at 6:56 PM Yaroslav Halchenko notifications@github.com wrote:

up to you -- it is your project(s). just know that your users (and outsiders like me) would only appreciate additional effort of the mighty git tag (at least) or pressing a button on releases pages

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.