launchpad development
Rationale
Currently we have a release once a month that release unfinished features to. launchpad.net. The ones using launchpad.net hasn't signed up to be beta testers, and thus shouldn't be among the first to try out the feature. Aligning the development of a feature to our release cycle is hard.
Stakeholders
Launchpad developers: Mail sent to launchpad-dev.
Launchpad users: hard to have a discussion with all the users that are. affected. At least we give them a choice of using either edge.launchpad.net or launchpad.net.
Constraints
Allow a feature to exposed to edge.launchpad.net only, even if we rollout db changes to launchpad.net.
Must be able to review the list of features that are exposed on edge but not on launchpad.net.
Need to keep track of which revisions on edge haven't been pushed out to launchpad.net yet.
- Must not slow down the current development process.
Out-of-scope
- Features that require database schema changes
Nice-to-have
Obvious when looking at edge that a feature is new and warrants feedback
Workflows
See MergeWorkflowDraft.
Success
When we can update the db schema without rolling out features under. development, and the Launchpad developers haven't gone mad from crazy process changes.
Better quality features released to production.
