remove mailman.beta_testers_team from config

Could we make this three steps?
Set the key on prod to be the regular beta users team.
Delete the email beta team.
Delete the config key etc.
?

This would delete the beta mailing list team sooner, and decouple
doing that from the slightly tricksy prod config schema update.

On Mon, 2010-08-16 at 20:03 +0000, Robert Collins wrote:
> Could we make this three steps?
> Set the key on prod to be the regular beta users team.
> Delete the email beta team.
> Delete the config key etc.

I think this scenario is more work. Deleting the config key from the
schema will invalidate any config that uses it. No config uses it; the
value is inherited from the schema. So we do not need to update any
production configs, or development.

There is no code that uses this key, no code that knows about this team.
Presence in the team was the guard for showing the create mailing list
link. I think we can be conservative by removing the keys from the
schema. When staging updates, we can delete the team to verify nothing
unexpected happens. We can delete it from lpnet when it rolls out.

We could ignore the schema step since nothing expects it: Delete the
team on staging, verify nothing surprising happens, then do the same
from lpnet. We can correct an issue by creating a new team named
mailing-list-beta-testers.

Makes sense to me.

Fixed in stable r11391 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11391>.