2.0 release plan

[rawpixel-vincent]

I'm up to help to get out a new version of this library, the last commit was 3 years ago and still some people using this library, my thought is to get a new major release out as soon as possible, with as less as possible breaking changes to address the current issues, then focus on a new major release for the long term.

Here is my thought for the 2.0 release:

• triage the opened issue and flag any bugs as 2.0, includes any nice to have new features that doesn't require fundamental changes to the code base
• target the node 12.x and fix deprecated warnings / leverage new language features
• run security audit and upgrade any libraries as needed
• refactor existing tests and add tests coverage for configuration options and different status code response.
• update the readme with workaround for some issue that can be solved without changing the existing code.

Then open a new branch for a 3.x release that allows breaking change and target current node LTS version

[rawpixel-vincent]

I have no clue, but going through some issues, I can see some desperation, I'll give it a try to flag all contributors listed in the readme, in case someone can help to contact and unlock this repository.
Let's resurrect that repo !!
@faceair
@rv-kip
@amaurigabriel
@benmcmeen
@pwmckenna
@mattberther
@RSNara

[rawpixel-vincent]

I haven't got much feedback so i decided to went the hard road of a 2.0 on a fresh fork - I'm targeting an alpha by next week which would be just the current pending PR merged into master and working - then it's a road to 2.0 with a decent test coverage for the existing feature.
and then well ... then if it happens - works towards 3.0 with breaking changes for the best.
anyone willing to help please make some noise ❤️

[rawpixel-vincent]

https://github.com/rawpixel-public/express-redis-middleware