Skip to content

Launch ops: Freemius products, repo rename, domains, update-worker catalog, .org SVN #8

Description

@ifahimreza

Launch ops tracking — user + ~1h assist (runs in parallel; Freemius product creation ideally lands before A5 so real IDs ship in the release zips)

External/manual tasks for the Outbees → Mailyard Pro launch. Code ships dormant-safe without these (both Freemius inits no-op on blank credentials), but licensing/updates only go live once they're done.

Freemius dashboard

  • Create parent product Mailyard (slug mailyard, free, add-ons enabled)
  • Create add-on Mailyard Pro (slug mailyard-pro, parent = Mailyard, paid plans + 3-day no-payment trial; confirm pricing)
  • Paste the four values into code: MAILYARD_FS_ID/MAILYARD_FS_PUBLIC_KEY (mailyard/includes/freemius.php) and MAILYARD_PRO_FS_ID/MAILYARD_PRO_FS_PUBLIC_KEY (mailyard-pro/includes/freemius.php)
  • Upload mailyard-pro-0.1.0.zip as the premium deployment artifact

GitHub / infra

  • Rename repo plugpressco/outbeesplugpressco/mailyard-pro (redirects preserve issues/remotes; update local remotes anyway)
  • Update PlugPress HQ board cards + any issues referencing Outbees
  • plugin-update-workers: remove outbees from catalog.json (self-hosted update channel is dead for this product)

Domains / marketing

  • mailyard.co: /docs, /support, Pro/pricing page (code + readme link to these)
  • 301 outbees.co → mailyard.co
  • Update site copy: retire the "no Pro version, ever" promise per the A3 framing ("everything in Mailyard stays free — Pro adds broadcast campaigns")

WordPress.org

  • Release free Mailyard 1.1.0 via SVN: Freemius SDK + == External services == disclosure + rewritten Pro positioning — expect reviewer attention on the SDK addition
  • After Ship 2: 1.2.0 release with new screenshots (top-level menu)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions