Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Roadmap for 2019 and beyond #206
The most recent release of this project, 2.3, is a fairly mature API. I became a dad recently, and won't have as much free time to building new features, so I'm not planning to do a bunch of work. That doesn't mean this library is dead, but it means I'm hoping improvements will be driven by your efforts. As a result, the future of this project will be guided by these principles:
This project began because the ASP.NET Core team decided to completely halt work on Microsoft.Extensions.CommandLineUtils. As I explained in my history and purpose post in 2017 (see #1), my primary objectives were to (1) fix some bugs in the original API, (2) make some minor improvements to the existing API, and (3) maintain this library so it keeps up with .NET churn, like new platforms and language features. I believe I have accomplished most of what I set out to do in terms of bug fixes and improvements, so the objective now is mostly to maintain this project.
I think it's also worth repeating the "non-goals" from the history and purpose post. These are still not goals.
By the way, that last part is no longer true. The .NET team has made available System.CommandLine: https://github.com/dotnet/command-line-api. The API is still experimental, so I won't endorse it as a production-ready API yet, but it shows promise and I recommend giving it a try.
Happy New Year, and thank you for all your contributions.
referenced this issue
Jan 24, 2019
Actually reading through this issue again, I guess there isn't stricly a conflict, but the README makes no mention of things like "The most recent release of this project, 2.3, is the last version of this library I am planning to work on." and other pertinent things in this issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please comment if you believe this should remain open, otherwise it will be closed in 7 days. Thank you for your contributions to this project.
@adamralph sorry I missed your comment. For more context on this issue (and why I missed your question), I had my first child a few months ago. As you can imagine, I don't have as much free time anymore.
Allow me to clarify - the primary goal of this announcement was meant to communicate that the pace of development here is going to slow down. It was not my intent to say that 2.3 is the last version of this library ever. I will still take contributions and make improvements, but I am looking for community interactions and PRs to take a lead.
So, if there is something you really want to see improved of changed, please let me know. I really am eager to take PRs and talk about ways to improve the library :)
I'd like to maintain ownership. I don't see this library as dead and I will occasionally make improvements. For instance, I was actually just thinking last night that I should try updating this library to C# 8 and incorporate nullable reference types.
That said, if my reduced attention to this repo caused things to stack up, I would be open to adding collaborators who have access to merge PRs, manage issues, and push code. That hasn't been the case so far...I've been able to keep up with the trickle of issues and PRs over the last 4 months.