Question about current status of this library (is it maintained?)

[lsegal]

Apologies for breaking the ISSUE_TEMPLATE here, but I'm not sure it applies, since this is more of a question than a feature request / bug report.

It's been a while since any updates have been made on the v2 or v3 roadmaps, and it seems like formidable is still released on npm as 1.2.2, which formidable's own README on npmjs lists as "deprecated". According to #412, none of the maintainers have current access to npm in order to publish updates(??), and there seem to be 2 different major versions under active development (#718 and #635), with oddly v2 being the later discussion(?).

Based on the above I have a few related questions as we try to determine if we should be using this library, or an alternative:

1. Do any of the current maintainers of this library have up-to-date access to publish npm updates to the formidable package on npm?
2. If yes to the above, is there a reason the current npm package is not at least in sync with the latest 1.x branch? i.e., according to this comment, the current latest release should be 1.2.3.
3. Will the next release of formidable be made as v2, or v3? Which branch should users following development be tracking?
4. Related to the above but mostly because I'm not in the loop here, are there any links / resources on why there are 2 major versions being actively developed (but not yet released) at the same time?

Thanks in advance!

[GrosSacASac]

1. No Becaue I can't publish on npm formidable, However I do publish on my npm in the meantime @grossacasacs/formidable

3. v2 (soon haha) and then shortly after v3. Users should use v3 in my opinion
4. Only v3 is being developed, v2 is ready for release and did not have changes made in the last couple of months, the reason I started v3 is to separate it from v2 since it does have a couple of breaking changes

[GrosSacASac]

Continue here #412,
I can give you access if you want

[tunnckoCore]

@lsegal

1. yes, me (not that active but keeping up from time to time) and @GrosSacASac who have problems publishing from npm, because of 2fa stuff.
2. the 1.2.3 is nothing much different that 1.2.2 anyway, i think the 1.2.2 was the readme update mentioning the development of v2 and v3, but it may very well be the 1.2.3 version, don't remember.
3. and 4) v2 as next latest for some time, v3 is got/getting more breaking changes since v1 & v2. I liked the raw changelog and the whole reason i put every single change in the Changelog was to be able to see the massive work that was done through the process - 150+ issues and PRs were closed/fixed. Initially or at some point I/we thought to release v3 and skip v2. The whole reason v2 should exist is for gradual update, because it doesn't really have true "breaking changes" but was for insurance, where v3 is more drastic updates and new ideas.

So, v2 as the next latest dist-tag for some time, and v3 as v3 or canary or dev dist-tag, then we'll move v3 to latest and mark v2 as deprecated in npm.