Marmelator/pdf.js
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixes

Tim van der Meij 2017-04-23 17:01:19 +02:00
parent e1370cc09d
commit 8d6877245b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Frequently-Asked-Questions.md

@ -189,7 +189,7 @@ The version number consists of three digits: the major release number, minor rel
We are moving fast and trying to land as much good stuff as we can review and test. The [generic viewer](http://mzl.la/pdf-js) always contains the latest PDF.js build and is available for testing.
During cooldown period, about once or twice in 6 weeks, we push our library to the [Firefox Nightly](http://nightly.mozilla.org/) channel. We decided to tag/mark our master branch each time we do that, and at this point a beta release is created. To promote a latest beta to a stable release, we listen for feedback (via [github](https://github.com/mozilla/pdf.js/issues), [bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=PDF+Viewer) or [IRC](irc://irc.mozilla.org/%23pdfjs)) from the users and projects that use PDF.js library. If no critical issues (e.g. a build is unusable, majority of the documents cannot be rendered, etc.) appeared, we promote the build as stable. Otherwise we either discard the release by replacing it by new beta or redo the build with commits that fix a critical issue.
During cooldown period, about once or twice in 6 weeks, we push our library to the [Firefox Nightly](http://nightly.mozilla.org/) channel. We decided to tag/mark our master branch each time we do that, and at this point a beta release is created. To promote a latest beta to a stable release, we listen for feedback (via [GitHub](https://github.com/mozilla/pdf.js/issues), [Bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=PDF+Viewer) or [IRC](irc://irc.mozilla.org/%23pdfjs)) from the users and projects that use the PDF.js library. If no critical issues (e.g. a build is unusable, majority of the documents cannot be rendered, etc.) appeared, we promote the build as stable. Otherwise we either discard the release by replacing it by new beta or redo the build with commits that fix a critical issue.
<a name="optimize"></a>
## What types of PDF files are slow in PDF.js? Can I optimize a PDF file to make PDF.js faster?