Adobe Acrobat Sign plans to deliver at least three releases each year, categorized as "major" or "minor" releases. Additional minor releases may be introduced to resolve customer-facing or system-processing issues as needed.

Major releases contain large-scale updates, impactful new features, and a larger volume of minor updates and experience changes.
Minor releases are added to the schedule as needed and when a launch date is established. Minor releases generally include smaller features and experience adjustments. Typically, there is one minor release between the major releases.

Note:

In the spirit of continuous improvement, Acrobat Sign will be releasing features not only in our major releases but also in minor releases (usually one minor release between each major release). To avoid disruption, we will continue to have these features behind enablement flags, meaning an account or group admin must explicitly turn them ON (check a checkbox).

Customers in the Health and Life Sciences field that require specific compliances should note that Acrobat Sign coordinates with a third-party vendor to provide a validation package for every release containing features to minimize your risk factor.

The prerelease schedule and notes are listed below.

Documentation

Documentation for release notifications and new/updated content is typically published as follows:

6-8 weeks before the production release (typically four weeks before the Sandbox launch), a summary of the expected features and updates is published on this prerelease page.
- If features are added or removed from the release after this point, they are noted in the Errata section at the bottom of the page.
- Resolved issues are not published at this time.
2-4 weeks before the production release (typically in alignment with the Sandbox launch), this prerelease page is updated with links to complete documentation of all new features and updated content.
- Links to the prerelease support documentation are provided on this page as needed. Prerelease documentation is in US English only.
- The first draft of the Resolved issues section is added. Resolved issues will likely change and be updated throughout the next four weeks.
Launch day, the official release notes are updated to reflect the newly published features and updates with links to the production support documentation. This prerelease page is updated to remove the launched content and showcase the next release.
- The documentation is published after the release is complete, and functionality is verified in the live system. This takes a variable amount of time, depending on the amount and complexity of the new content. The official publication should not be expected before 7pm Pacific time and may be significantly later.
- The complete list of Resolved issues is updated in the US English version of the release notes. Localized versions may have out-of-sync data due to localization.
Government Cloud updates typically happen one or more weeks after the production release. Due to the nature of the government environment, some features may need additional evaluation before enabling them.

Note:

Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).

When the release is published, the new pages will also be published, and links will properly resolve to their production URLs.

Sandbox availability

Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.

The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
The Sandbox environment uses the same status page and outage procedures as the regular Production environment.