-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification on 2.1 going non-beta? #10819
Comments
There's generally very little difference, as far as stability is concerned, between the stable/pre-release versions (since no code lands without e.g. all tests passing). |
I do agree that we should make a new release again. @brendandahl If we follow the release process, does the existing pre-release automatically become stable (on GitHub and NPM) or do we need to do that ourselves somehow? |
In that case, how about making sure that #10794 is landed first? |
If everything is working correctly it should. |
Yes, I agree. Those three are mostly done, other PRs can wait. @brendandahl Could you fix up your two PRs? |
I'm waiting for that too, but it seems it got stuck. Would be great to get a new release soon |
I'm planning to make a new release next Wednesday. |
Version 2.1 is now stable; refer to https://github.com/mozilla/pdf.js/releases. |
I just need a clarification for when 2.1 is going non-beta. I also noticed that the demo version is running 2.2.x. I assume 2.2.x is alpha?
The text was updated successfully, but these errors were encountered: