Beta banner should be available after a feature is widely available

Bug #905420 reported by Matthew Revell on 2011-12-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

The beta banner offers us a cheap way of announcing new features in Launchpad. It is also possible that we'll want to consider a feature as still in beta, even once it is available to all Launchpad users.

As such, it would be nice for the beta banner to be available even after a feature has been made available to everyone.

Deryck Hodge (deryck) wrote :

To be clear about the issue here:

The beta banner does some magic to know that the flag is not enabled for "default" and considers that as "beta." If we enable the feature flag for default to turn it on for everyone, there's no way to keep the beta banner around as a cheap notification mechanism.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
Abel Deuring (adeuring) wrote :

A possible workaround in some cases: The feature can be enabled for a scope that covers all affected pages, regardless of the users. As long as the default value of the feature flag (as defined in flag_info in lib/lp/services/features/flags.py or as defined as the default scope), the beta banner will be displayed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers