Development Status Disclaimer

[Iquiji]

No description provided.

[codecov]

Codecov Report

Merging #201 (09ae075) into master (8948c5d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #201   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          413       412    -1     
  Branches        57        57           
=========================================
- Hits           413       412    -1     

Impacted Files	Coverage Δ
src/test-loader.ts	100.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9e35d0c...09ae075. Read the comment docs.

[calebcartwright]

Thanks for sharing your perspective, but I'm going to close this as I firmly disagree with the assertions being made.

There's a big difference between intentionally and categorically stopping vs. how much time volunteers are able to allocate to a project. The fact that I'm currently stretched thin across a number of other projects is simply a reflection of the reality of open source volunteerism and the limits of there only being 24 hours in a day.

It's not that development has been halted by any stretch, and I'd point to cases like #186 where continued development are actively being discussed and where changes would be merged and released. The fact that I'm not personally pushing commits at the moment is completely orthogonal.

Thanks again, and feel free to consider contributing yourself if you're interested and/or would like to see certain features implemented!

[Iquiji]

Hey,

Thanks for responding so quickly!
I am sorry if i offended you by this.
I think i misunderstood the activeness of this project, because no updates were made in 3 years.

Iquiji

[calebcartwright]

No worries, and no offense taken!

Just want to stress the difference between there not having been much past activity vs. blanket statements about the future. There definitely could be future enhancements/fixes/etc., but whether there will be will probably be dependent upon the community (as often ends up being the case with free open source tooling).

The only way we'd officially say the extension is done and definitely won't receive any future updates would be if Rust Analyzer decides to add such Test Explorer functionality natively, but unless/until that happens we're still open for business (just very, very slow 😉)