LIOSFERAINDEPENDENT SOFTWARE
RU Contact us
Menu
Home / Updates / Release policy
LIOSFERA / RELEASE GOVERNANCE

How LIOSFERA verifies software releases

An editorial and technical approval process, not a statement that current plugins have passed release checks.

Product Units Free 1.1.0 is available directly from LIOSFERA, not yet WordPress.org. These requirements describe WordPress.org submission and future releases of other plugins.
  1. LIOSFERA

    1. Freeze a candidate

    Identify the precise source commit, tagged candidate and supported WordPress, WooCommerce and PHP matrix. Verify licence, files, readme and version consistency.

  2. LIOSFERA

    2. Run compatibility and security gates

    Run automated tests, WordPress plugin checks, installation and upgrade/uninstall trials, permissions/privacy reviews, and independent browser checks across supported environments.

  3. LIOSFERA

    3. Confirm a distributable package

    Rebuild the ZIP from the approved source, review its contents and checksums, check the documented changelog, and have a responsible maintainer approve the candidate.

  4. LIOSFERA

    4. Publish only after confirmation

    A maintainer separately submits or publishes to WordPress.org. Publisher-hosted verified stable ZIPs may be distributed separately; claim a WordPress.org listing only after directory approval and actual publication.

  5. LIOSFERA

    5. Record and monitor

    Preserve immutable build identifiers, link the verified changelog and release source, watch for regressions and publish corrective notes without altering past claims.

No automatic push from the development repositories is configured. No unapproved release tags, downloads, prices or subscriptions will be generated by this website.

← Development updates

Current readiness snapshot →