Open Stack

> 
> I think the importance of string freeze for server projects (e.g., cinder,
> nova, keystone, neutron) might
> be less important than previous cycle(s), but sharing the status to all the
> teams including release management team
> is a good idea to stay on the same page as much as possible :)
> 

Hey Ian,

Do you think we should make any changes to our policy for this? Just one thing
that comes to mind, for server projects should we just send out a ML post with
something like "Here is a list of patches we deemed important that had string
translations".

Just thinking of how we can keep things moving when needed while still making
sure important things are communicated well.

Or is that even too much? During soft string freeze, should the server project
core teams just try to be more aware of these but just approve patches that
are important fixes and move on?

Thanks,
Sean