Production release QA checklist
Add a built-in checklist before publishing a release: ZIP integrity, manifest metadata, Joomla/PHP/database compatibility, checksums, changelog XML and download policy validation.
Global platform direction for Joomla update delivery, package relationships, changelog intelligence and commercial release operations.
Current delivery work and active stabilization.
Add a built-in checklist before publishing a release: ZIP integrity, manifest metadata, Joomla/PHP/database compatibility, checksums, changelog XML and download policy validation.
Validate generated <changelogurl> feeds against Joomla requirements: element, type, version, supported nodes and enabled changelog items only.
Complete the parent product workflow for language packs, dependent add-ons, bundled libraries and optional artifacts with clearer public and admin screens.
Improve Markdown import for long text, metadata lines, duplicate detection, replace/append modes and safe preview rendering.
Near-term work queued for upcoming product iterations.
Generate ready-to-copy Joomla manifest snippets for <updateservers> and <changelogurl> using the configured update feed URLs.
Add release channels such as stable, beta, nightly and LTS with per-extension policies and public/private feed URLs.
Visually map package releases to exact child versions: plugin, module, library, file/language pack and template artifacts.
Add expiring signed URLs and access tokens for private releases, customer-specific builds and protected update feeds.
Import extension records, versions, type, element, folder, client and language metadata directly from uploaded Joomla manifest XML files.
Larger capabilities planned after current priorities.
Add charts for download cohorts, latest release adoption, extension usage, Joomla/PHP version split and failed update attempts.
Connect repositories, read release assets, verify ZIPs, import changelog text and stage releases for review.
Trigger release import, feed refresh, cache purge and notification workflows from repository or CI/CD events.
Support paid downloads, customer entitlements, subscription status and license-aware update feeds.
Prepare vendor pages, public product profiles, support links, documentation hubs and branded download areas for future marketplace mode.
Ideas and candidates not yet scheduled.
Allow release ZIPs to be stored in S3-compatible storage while keeping secure download tracking and checksum validation in ExtensionFlow.
Move heavy ZIP validation, checksum generation, manifest inspection and repository imports into queued jobs.
Add organization workspaces, vendor teams, tenant-specific branding and isolated extension catalogs.
Add Spark commands for feed validation, stale file cleanup, checksum refresh, access-policy audit and seeded extension health checks.