← Back to team overview

openstack team mailing list archive

Re: Nexenta Driver proposal


Hello again, everyone.

We finally got our pass to integrate the driver with Essex release. What
should we do to target our blueprint to Essex release to pass through
feature freeze at essex-3?
We're going to provide code no later than Feb 15, so we'll have enough time
to be ready before code freeze at essex-4.
My guess is that our blueprint should be approved and targeted at essex-4,
can somebody do that?

Kind regards, Yuriy.

On Tue, Nov 15, 2011 at 21:58, Caitlin Bestler

> Passing standard integration tests that shows an option dealing with a
> special installation has no adverse
> effect on a reference environment makes sense.
> It may be possible to support central test equipment in this case, but
> that will definitely not be the
> case for every possible enhancement. We probably need to also talk in
> terms of test scripts that
> come from the central team that you expect someone supporting an option to
> run on their own
> test equipment.
> How often would such a remote test be needed? After each nightly build
> might be a bit too often,
> and only once per release cycle might not be frequent enough.
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp