Not ideal because we also have the real usecase for community images. When users start to create/use community images these different use cases (old public and real community) will be mixed. Cheers, Belmiro On Wed, 27 Sep 2017 at 15:37, Blair Bethwaite <blair.bethwaite at gmail.com> wrote: > On 27 September 2017 at 22:40, Belmiro Moreira > <moreira.belmiro.email.lists at gmail.com> wrote: > > In the past we used the tabs but latest Horizon versions use the > visibility > > column/search instead. > > The issue is that we would like the old images to continue to be > > discoverable by everyone and have a image list that only shows the latest > > ones. > > Yeah I think we hit that as well and have a patch for category > listing. It's not something I have worked on but Sam can fill the > gaps... or it could be that this is actually the last problem we have > left with upgrading to a current version of the dashboard and so are > effectively in the same boat. > > > We are now using the “community” visibility to hide the old images from > the > > default image list. But it’s not ideal. > > Not ideal because you don't want them discoverable at all? > > > I will move the old spec about image lifecycle to glance. > > https://review.openstack.org/#/c/327980/ > > Looks like a useful spec! > > -- > Cheers, > ~Blairo > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170927/d62f8b3b/attachment.html>