Ship and announce a feature
Release a merged feature with a gated workflow, then tell people with a launch post, a walkthrough, a deck or a film.
"Keep the cart across devices" is merged at Northwind. Adam releases it. Lena tells shoppers and the rest of the company. This page covers what EasyCode gives you for both, and says where your own tools take over.
Before you start:
- Workflows run in sessions in the desktop app, on your own harness login.
- Decks, films and walkthroughs live in the Studio, which needs the
studiomodule. EasyCode staff can stop it with thestudiokill switch. - Making something in the Studio needs a full member and a desktop app signed in for you.
Release it
Run the release workflow
EasyCode's Release and roll back template covers the release. Publish it once from Workflows → Start a workflow, filling in how your repo releases and where it deploys. See Workflows, gates and the board.
Adam starts it on a release task with Run workflow. Its steps:
- Run the gate: your repo's own check. If it fails, the run stops and nothing is released.
- Write the release notes: what changed since the last release, grouped by what users notice, with any migration, setting or breaking change flagged. The notes are a document on the task.
- Approve the release: a gate. The team lead reads the notes and approves, or requests changes, which sends the run back to the notes.
- Release: with the repo's own mechanism, naming the version.
- Watch it and Is it healthy: check the key flows. If it isn't healthy, Roll back returns to the last good version and writes down what failed.
Plan a risky rollout first
If the change is risky or touches data, the DevOps role pack's Plan a rollout skill writes the stages, the checks between them and the way back. Ask for it in a session before the release run.
EasyCode drives your repo's own release mechanism. It doesn't host your deployments.
Announce it
Write the launch post
With the Marketer role pack in your kit, a session has the Write a launch post skill. It collects facts from the merged changes, the spec and the release notes, writes only what shipped, and offers a title, a short summary for social posts and a line for your changelog. Lena reviews the draft in a task document. See Write a spec with your team for how review works.
Show the change
On the Studio's Make something page, Lena picks a product and what to make, then writes what it should show:
- Walkthrough of a pull request: the change in reading order, with proof, pinned to the pull request's head.
- Deck: slides at 1920 × 1080 with present mode. Export PDF saves it as a PDF.
- Film: from a beat sheet or a pull request, with voice, music and sound effects.
Each choice starts a session with its skill. Your own harness does the drawing.
Render the film
Desktop app only
Films render in the desktop app. Open the film's render panel and press Render master (16:9) or Render square (1:1). Each makes a 1080p30 MP4 and lists it under Renditions.
Share it
Press Share on the artifact to add people, teamspaces or products. To reach people outside the org, make a view-only link: only a published version can have one, and someone must press Mark as safe first, which is recorded with their name. Anyone with the link can read that version, with no account, no comment box and no download. Turn off link stops it. See Share and review in the studio.
Post it in your own channels
EasyCode doesn't post to your blog, changelog or social accounts. Copy the launch post, the PDF or the MP4 into the tools your team already uses.
Is What's new for my announcements?
No. What's new in the app's top bar is EasyCode's own changelog: what changed in EasyCode itself. Your team's features don't appear there. To follow EasyCode's releases, read the changelog.
Related
Something wrong or missing? Suggest a change