← Back to team overview

launchpad-dev team mailing list archive

Thread
Date

Re: changing security.cfg in ReleaseFeaturesWhenTheyAreDone process

To: Robert Collins <robertc@xxxxxxxxxxxxxxxxx>
From: Jeroen Vermeulen <jtv@xxxxxxxxxxxxx>
Date: Wed, 10 Nov 2010 20:16:07 +0700
Cc: launchpad-dev@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTims7xtXvHRaaJFe1hjGo+WMGz_Gi7gsp7AFf1Tt@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6

On 2010-10-22 00:55, Robert Collins wrote:

security.cfg won't be applied, thats true, but you'll need
security.cfg to test this, and you need the code in devel to deploy
it. And we can do GRANTS live, we just can't run the entire thing.


Has that changed now, with the faster security.py?


Jeroen

Follow ups

Re: changing security.cfg in ReleaseFeaturesWhenTheyAreDone process
From: Stuart Bishop, 2010-11-11

References

changing security.cfg in ReleaseFeaturesWhenTheyAreDone process
From: Curtis Hovey, 2010-10-21
Re: changing security.cfg in ReleaseFeaturesWhenTheyAreDone process
From: Francis J. Lacoste, 2010-10-21
Re: changing security.cfg in ReleaseFeaturesWhenTheyAreDone process
From: Curtis Hovey, 2010-10-21
Re: changing security.cfg in ReleaseFeaturesWhenTheyAreDone process
From: Robert Collins, 2010-10-21