Anomaly in SharePoint's document control paradigm
In a traditional document control process, approval must take place before a version is created (for example, draft 3.9 is submitted for approval, and only after it is approved does it become version 4.0). When working with SharePoint's approval function, major versions are created before they are approved.
Because Hyper.Net only publishes approved versions when versioning has been enabled, it can occur that there are major versions in SharePoint that have not yet been published. This only makes sense, because an unapproved version should not be deployed to its target audience. In organizations experienced with tight document control, this can lead to the question "Why didn't Hyper.Net publish my version 4.0?" The answer: "Because it hasn't been approved yet in SharePoint."