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

Updated Frequently Asked Questions (markdown)

Yury Delendik 2014-04-18 07:30:00 -07:00
parent 597b8cf8c4
commit b22b51ec11
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Frequently-Asked-Questions.md

@ -149,10 +149,10 @@ Please periodically check or subscribe to our dev-pdf-js@lists.mozilla.org maili
<a name="version"></a>
## What is a latest stable version of PDF.js?
PDF.js is a general-purpose library to parse and render PDFs. At the moment it's included in the number of projects such as Firefox, Firefox OS, Chromium Extension, etc. We are recording our changes to the library with Github [pull requests](https://github.com/mozilla/pdf.js/pulls) and the log of the changes is also available form the git log.
PDF.js is a general-purpose library to parse and render PDFs. At the moment it's included in the number of projects such as Firefox, Firefox OS, Chromium Extension, etc. We are recording our changes to the library with Github [pull requests](https://github.com/mozilla/pdf.js/pulls). Also the log of the changes is also available form the git log.
The version number consists of three digits: the major release number, minor release number and build number. The major and minor number are selected when some major milestone is reached. The build number is incremented by one each time when new a commit is pushed to the master branch. For sanity check, we accompany each version number with the SHA number of the latest commit.
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) and development of version of Firefox PDF Viewer [extension](http://mzl.la/pdf-xpi) are always contain the latest PDF.js build and available for testing.
During cool down period, at our discretion, 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 that point a beta release is created. To define a stable version we listen for a feedback from 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 will fix a critical issue.
During cooldown period, at our discretion, 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 that point a beta release is created. To define a stable version we listen for a feedback from 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 will fix a critical issue.