Release?

[Narven]

@ogham ogham released this on 15 Jul 2019 · 6 commits to master since this release
exa release v0.9.0

I will release more than one version of exa this year, mark my words.

Release?

[mschilli87]

too late 😆

[maximal]

:-)

[sluongng]

@ogham do we get a new release sometime soon?

[neilweidinger]

@ogham any updates? exa has been fantastic so far and have been loving using it, would love to see some of the latest commits be included in a new release :))

[noqqe]

New release would be very appreciated as of all the file time fixes @ogham @Freaky <3

[Narven]

[rpdelaney]

@ogham Is there anything community contributors could be doing to help support a faster release cadence?

[ethancedwards8]

:( I love this tool, I didn't realize it was dead, is there a fork that's maintaining it? Or someone to pass ownership too? Exa is still missing a lot of features but and I would love to contribute and help it but I see no point of the project is dead.

[lespea]

I wouldn't call my fork "maintained" but I did merge in a handful of patches and make a few other changes: https://github.com/lespea/exa

[cristaloleg]

Kindly bump :)

[kovetskiy]

@lespea your repository doesn't have Issues tab (is it only for me?). Also, could you please highlight what changes did you make and update installation instructions? Look forward to giving a try to your fork!

[lespea]

I enabled issues, I think they weren't on by default because I just forked this repo? Basically started with the pmeta branch (included some threading enhancements), merged PRs 2, 3, 4, & 5, and cleaned up the code + fixed clippy issues + updated to the latest deps.

[ariasuni]

Hi @lespea, I’ve been added recently as contributor of this repository. This means I can do a few things like closing issues and merging PRs. I would be glad to review and merge your work «officially» so that it can be part of a release someday! :)

Anyway, let’s close this in favor of #673.