Fd: Discussion: Stabilization phase?

Created on 7 Jun 2020 · 1Comment · Source: sharkdp/fd

I personally feel like we reached a point in the development of fd where we could take a longer break from introducing new features (especially breaking changes) and focus on stabilization instead. I would like to know what others think about this idea.

There are a few things which I would like to get finished before we start this phase (in particular: #612).

Once we enter the stabilization phase, I would like to focus on three major things:

Bug fixing
Documentation improvements
Performance improvements

I would not put a super-strict ban on new features, but I would probably reject larger-scale changes for a while. Especially those that are likely to introduce new bugs.

What do you think? If you think this is a good idea, what kind of feature requests / breaking changes would you like to see implemented before we would start such a phase? If not, what do you propose instead?

help wanted question

Source

sharkdp

👍7 👀1

Most helpful comment

+1 for stabilization phase. Long-time fd user here, zero complaints and I think the UX is absolutely first class (takes a tiny bit getting used to if you come from GNU find). I don't think there are any additional features I've ever wished fd had.

Regarding https://github.com/sharkdp/fd/issues/612 I've had fdh: aliased to fd --no-ignore-vcs -H -E '.git/' for a long time, and think it's a good resource-saving default, but also wouldn't mind if I had to make an alias to do the inverse.