On 2016-02-03 03:27, Dmitry Borodaenko wrote: > [...] > Level 1. Plugin is actively supported by Fuel team > > As we expand plugin capabilities and move more functionality from Fuel > core into plugins, we will inevitably get to the point where some > plugins are required to successfully complete even a basic deployment > (aka "pass BVT"). Even before that, we may decide that some plugins are > important enough for our reference architecture to allow the state of > these plugins to affect our release cycle: allow Critical bugs in them > to affect Fuel release, cover them in acceptance testing for Fuel > releases and maintenance updates, and so on.
> Obviously, whole Fuel team is expected to support such plugins, and is > self-motivated to provide timely help to their maintainers to keep them > healthy. In addition to the expectations from the previous support > level, we should track the list of these release-critical plugins in the > policy section of fuel-specs [7]. So, these are plugins that will be officially part of fuel team? You depend on it for successful installation... Andreas > [7] https://git.openstack.org/cgit/openstack/fuel-specs/tree/policy > > Thoughts, comments, objections? > -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
