[
https://issues.apache.org/jira/browse/SOLR-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902247#comment-14902247
]
Upayavira commented on SOLR-7858:
---------------------------------
Thanks [[email protected]] for your rich perspective.
Firstly, to answer your question: yes, the new UI has been in trunk/5x since
5.2. As to whether it has been functional, there are a lot less bugs than there
were, although you are right to observe that it needs usage.
= o =
URLs:
In your comments you were concerned about how a user would be able to find out
which UI they are using and what the purpose of the change is. I've added links
at the top right of the old, and new UIs to switch between them, and a (?) link
that points to a wiki page explaining further. I hope this does sufficient in
terms of messaging - although your suggestion of a banner saying "this is the
old UI, go try the new one-->" seems like a good idea.
Personally, I'd support a redirect from http://localhost:8983/ and
http://localhost:8983/solr/ to http://localhost:8983/solr/admin/ and host the
entire UI there. You mention the risk of URL overlap, but we already have that
issue, in more dangerous ways, with files in the UI using the URL space that
end-users access. At least if we switched to /admin/, we would only be in
conflict with ourselves, in which case it is infinitely more manageable. And,
it is already pretty much a given that 'admin' wouldn't work as a collection
name.
I would, however, suggest we keep this for trunk/6.0. As a code change, it is
small. As a usability one, it is much bigger.
= o =
Based upon your suggestions, my release proposal and schedule would be:
* 5x already has links between old/new UIs so users of 5.4 will be able to get
to the new one easily
* There is also a ? link that points to a wiki page explaining the change and
asking for bug reports
* Add a banner saying "go try the new UI" on the old one, both in trunk and 5x
* Change URLs in trunk straight away so that the new UI is the default (old
one as /original-ui.html)
* Add a note in CHANGES.txt for 5.4 stating clearly that it will become
default in 5.5.
* Assuming no major clangers, for 5.5, change the URLs to make the new default
(old one is /original-ui.html)
* For trunk, change the UI to serve from /admin/. Files remain in the same
location.
> Make Angular UI default
> -----------------------
>
> Key: SOLR-7858
> URL: https://issues.apache.org/jira/browse/SOLR-7858
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Reporter: Upayavira
> Assignee: Upayavira
> Priority: Minor
> Attachments: SOLR-7858.patch, new ui link.png, original UI link.png
>
>
> Angular UI is very close to feature complete. Once SOLR-7856 is dealt with,
> it should function well in most cases. I propose that, as soon as 5.3 has
> been released, we make the Angular UI default, ready for the 5.4 release. We
> can then fix any more bugs as they are found, but more importantly start
> working on the features that were the reason for doing this work in the first
> place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
