Release manager
Know what's in the release. Ship every application together.
Productmind opens a pull request for each application, finds the tasks, bug reports and sessions in its commits, and drafts the release notes. Release merges and tags them all, or one application at a time.
Email reminders and amounts due
3 pull requests12/12
Instalment reminders now go out by email too, and every invoice shows the amount still due.
Highlights
- Email reminders: each instalment reminder is also sent by email.
- Amount due: every invoice shows what is left to pay.
- Fixed: the second instalment shows the right due date.
In this release
Read a release as the work it ships,
not as a list of commits.
Productmind finds the work in the commits: from the coding sessions that made them, and from IDs such as TASK-12 or BUG-3 in their messages. It lists the tasks, bug reports and sessions under the feature each belongs to, and drafts the release notes from the same commits.
Email reminders and amounts due
Meet Software Inc, a fictional company that sells invoicing software. Every name in these pictures is sample data.
Each item names its commit.
Every item Productmind found shows the short ID of the commit it came from. Choose it to open the commit.
Add what the commits don't say.
Add a task, bug report or session by hand, and it stays on the release every time it is refreshed.
Your notes are never overwritten.
Once you've written notes, a new draft waits for your review instead of replacing them. Productmind names the release from what it contains, unless you've renamed it.
Up to date while you prepare it.
The development branch keeps moving. Refresh compares the branches again, updates the commits and finds the work again.
Before you release
See what's ready.
Read what's risky first.
Each application's row says whether it can ship, and the line under it says why. Open a row to read its changes without leaving Productmind, starting with the files flagged high risk.
Email reminders and amounts due
3 pull requests11/12
Email reminders and amounts due
Email reminders and amounts due
Sample data
Release
All at once,
or in the order production needs.
Release writes the notes into each pull request, merges it and tags the merged commit with the release's ID. When your production pushes must follow an order, release one application at a time, then Release the rest.
Release anyway, within your rules.
When checks are failing or still running, Release anyway names what isn't ready before it merges. Your branch protection rules still apply, so a merge your Git provider refuses fails on that row.
One failure doesn't stop the rest.
Applications ship one by one. If one merge fails, the others still ship, and releasing again ships only what isn't merged yet.
Merged as you.
Connect your own GitHub, GitLab or Bitbucket account, and each merge it's allowed to make is yours. The row says who merged it, and the audit log records it.
Put it on hold.
Close closes every pull request of the release at once, without merging or deleting anything. Re-open brings them back, with the same numbers on GitHub and GitLab.
A person presses Release.
An AI assistant connected to Productmind, or an API key, can't release, close or re-open a release. Those need someone signed in.
Email reminders and amounts due
3 pull requests12/12
Instalment reminders now go out by email too, and every invoice shows the amount still due.
Highlights
- Email reminders: each instalment reminder is also sent by email.
- Amount due: every invoice shows what is left to pay.
- Fixed: the second instalment shows the right due date.
Sample data
After it ships
When it reaches production,
your product knows.
Merging to your production branches starts your deployment pipelines. When your pipeline reports that the release reached production, the release becomes Released and the features it shipped move to Stable.
Traced both ways.
Each coding session lists the releases its work shipped in. On plans that include lineage, follow a release back to the customers who asked for it.
Announced in Slack.
If your workspace posts events to a Slack channel, new releases and status changes appear there.
Deployed to AWS, on Enterprise.
In early access, an application started from a template can deploy each environment to an AWS account Productmind manages for your workspace, or one your company connects. Every pull request merged into the environment's branch deploys.
Read moreLineageCloud accounts
Pay in instalments
Lineage · Pay in instalments
RequestPFR-5
Split large invoices
Promoted6 customers
FeatureFEAT-3
Pay in instalments
Stable
PlanSSID-3
Payment in instalments
Completed
ReleaseREL-2
Instalment payments
ReleasedOct 16
Sample data
Tell your customers.
Share on LinkedIn writes a post from the release notes, the features the release shipped and your workspace overview. Edit it, and Open LinkedIn copies it and opens LinkedIn with it filled in.
Instalment payments
1 pull request4/4
Customers can now pay any open invoice in three equal instalments.
Highlights
- Instalments: three equal payments, one a month.
- Reminders: a reminder goes out 7 days before each instalment is due.
- Missed payments: the rest of the plan waits until it is paid.
Share on LinkedIn
A post written from these release notes and your product overview - the user-visible wins, for customers and people still evaluating you.
New at Software Inc: pay any invoice in three instalments.
Split a large invoice into three equal payments, one a month, and get a reminder a week before each one is due.
Try it on your next invoice at software-inc.example
Sample data