Excerpts from Thierry Carrez's message of 2017-09-21 17:10:52 +0200:
> Sean Dague wrote:
> > Agreed. We're already at 5 upgrade tags now?
> > 
> > I think honestly we're going to need a picture to explain the
> > differences between them. Based on the confusion that kept seeming to
> > come during discussions at the PTG, I think we need to circle around and
> > figure out if there are different ways to explain this to have greater
> > clarity.
> 
> In the TC/SWG room we reviewed the tags, and someone suggested that any
> tag that doesn't even have one project to apply it to should probably be
> removed.
> 
> That would get us rid of 3 of them: supports-accessible-upgrade,
> supports-zero-downtime-upgrade, and supports-zero-impact-upgrade (+
> supports-api-interoperability which has had little support so far).
> 
> They can always be resurrected when a project reaches new heights?
> 

On the other hand, some of those were meant to be aspirational, so not
documenting them may mean no one is thinking about them at all.

Doug

__________________________________________________________________________
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

Reply via email to