Update README to recommend master branch

[AmmoniumX]

I think the master branch is now solidly at a point where it is significantly more stable than 0.1.X, however, the README still directs users towards either the 0.1.X branch or the 0.1.8 tag, neither of which have been active in over a year.

This creates a negative experience for new users, especially this section:

It is suggested to either use the latest release tag or our release branch (which will get consistent updates) 0.1.x.

It is not suggested to run latest master.

There are many bugs/issues that have been fixed long ago that new users will likely run into due to this outdated information, e.g. #3487

I propose that the README is updated to recommend master over 0.1.X/0.1.8 so that new users can experience the smooth and less buggy version that is currently available

[mfxa]

Good suggestion. Another suggestion could be to make a release, and move any TODOs to the next release?

Edit: As I just noticed a release or your suggestion is also suggested on #3517 and #3422 and kinda #3438

[jamestrew]

telescope hasn't had much active development for some time now. The "stable" branch is actually just broken on neovim 0.11+ but master branch still has a ton of half baked things we wanted to polish (or even take out) but never got around to.

I don't think there's any maintainers remaining who regularly triage issues, review PRs, myself included. I think many of us have moved on from even using telescope.

Don't want to rule out the possibility of some sort of revival, but I think it's only fair to be upfront that telescope is effectively unmaintained at this point.
It's tragic seeing newcomers to neovim posting about long known telescope bug just as they're getting their feet wet. Especially when there are several very solid alternative fuzzy finders available today.

@Conni2461 @tjdevries

[mfxa]

Especially when there are several very solid alternative fuzzy finders available today.

Which good (better?) options are there?

[jamestrew]

Which good (better?) options are there?

I would say fzf-lua, mini.pick, snacks.picker off the top of my head

[mfxa]

Thanks for the recommendations! I have a LOT of telescope configuration so it would take a while to migrate but I am starting to consider it then.

I wonder if it would make sense to archive the project and then see if a fork emerges or not. It seems PRs are still coming in at least, so I wonder if there are some potential maintainers among them. Or they could be added here instead of doing a fork I guess.

[ssteinbach]

Putting a note about its dormancy in the README might be nice so folks at least know there aren't any maintainers active at the moment

[mks-h]

It'd be helpful to put up a notice in the README that this plugin doesn't work with the rewritten (main branch) of nvim-treesitter (#3487), and isn't receiving any updates.

[cubiquitous]

Would at least be OK to share in social media that the plug-in is currently not maintained?