launchpad-dev team mailing list archive

[Martin Pool <mbp@xxxxxxxxxxxxx>]

That's such a nice subject line I had to keep it.

When devel is next deployed, Launchpad will get a /+feature-rules
page, through which ~admins can configure feature flag rules, as an
alternative to losas updating them through sql.
<http://launchpadlibrarian.net/56727141/20100929-feature-control.png>
For instance if someone adds a flag to disable moving bugs out of
fix-released, we might add

  bugs.lock_fix_released  edge  100  true

where the fields are
 - the flag name, matching your call to getFeatureFlag
<http://people.canonical.com/~mwh/canonicalapi/lp.services.features.html>

 - the scope selector in which you want this value to apply

 - the priority of this rule, higher numbers being more important,
used when more than one scope could match for this flag

 - the value it will take, as a string

I encourage you to use this on launchpad.dev to interactively test how
your feature flags work.

Changes to the rules on production are governed by the
ProductionChangeApprovalPolicy (internal link:
https://wiki.canonical.com/Launchpad/PolicyandProcess/ProductionChangeApprovalPolicy)
which basically means that you should ask a team lead, project lead,
or technical architect, who will then ask a LOSA to actually make the
change.

-- 
Martin