created by @BlueFinBima on 2020-02-19 08:42:40 +0000 UTC
assignees: derammo
Currently CommandLineParser is implemented against their pre-V2 api. Code changes will be necessary to work with more recent levels. Since there is nothing broken, this is only needed for neatness because later levels of the package on NuGet are being flagged.
Comments:
comment by @derammo on 2020-02-20 00:05:49 +0000 UTC
I just reviewed Microsoft's offering to see if we can get rid of third party, and I don't like it (overly complicated attempt at making it look magical.) I recommend we just bump to latest version of what we have, assuming it supports the same formats (including --long=value with an equals sign, which I think it currently supports.)
comment by @derammo on 2020-02-25 14:42:39 +0000 UTC
@BlueFinBima I would like to do this work. What milestone are you thinking? Shall we have a release branch for Q1 so we can control what goes into it, or do you want everything else in forward branches?
comment by @BlueFinBima on 2020-02-25 15:10:40 +0000 UTC
I think this would be Q2 milestone unless you're real quick. I'm still
mulling over the future branch management, and release cotnrol. Happy to
take your advice.
@BlueFinBima https://github.com/BlueFinBima I would like to do this
work. What milestone are you thinking? Shall we have a release branch for
Q1 so we can control what goes into it, or do you want everything else in
forward branches?
comment by @derammo on 2020-02-25 15:22:57 +0000 UTC
I see zero reasons to add risk to the Q1 RC for this feature that affects noone :)
I want to do the work only so we get --help command line parameters that I can use to populate the list of command line options in the wiki. Priority couldn't be lower :).
Currently CommandLineParser is implemented against their pre-V2 api. Code changes will be necessary to work with more recent levels. Since there is nothing broken, this is only needed for neatness because later levels of the package on NuGet are being flagged.
Comments:
comment by @derammo on 2020-02-20 00:05:49 +0000 UTC
I just reviewed Microsoft's offering to see if we can get rid of third party, and I don't like it (overly complicated attempt at making it look magical.) I recommend we just bump to latest version of what we have, assuming it supports the same formats (including --long=value with an equals sign, which I think it currently supports.)
comment by @derammo on 2020-02-25 14:42:39 +0000 UTC
@BlueFinBima I would like to do this work. What milestone are you thinking? Shall we have a release branch for Q1 so we can control what goes into it, or do you want everything else in forward branches?
comment by @BlueFinBima on 2020-02-25 15:10:40 +0000 UTC
I think this would be Q2 milestone unless you're real quick. I'm still mulling over the future branch management, and release cotnrol. Happy to take your advice.
On Tue, 25 Feb 2020, 14:42 derammo, notifications@github.com wrote:
comment by @derammo on 2020-02-25 15:22:57 +0000 UTC
I see zero reasons to add risk to the Q1 RC for this feature that affects noone :)
I want to do the work only so we get --help command line parameters that I can use to populate the list of command line options in the wiki. Priority couldn't be lower :).
Let's talk about branching in chat.
migrated from https://github.com/BlueFinBima/Helios/issues/191
please make sure to close upstream issue when this item is closed