AngularJS 2.0 isn't fully baked yet, and is, as you suggest, a very
different beast. Given that level of change, you can expect a lot of 1.x
momentum once 2.0 is out.
The bulk of this project wasn't AngularJS coding, rather understanding
the intent of the existing code, and only then taking
Cool. This certainly answers my questions.
Thank you,
Alex.
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 21 May 2015 at 17:58, Upayavira u...@odoko.co.uk wrote:
AngularJS 2.0 isn't fully baked yet, and is, as you suggest, a very
Don't get me wrong, good question to ask!
On Thu, May 21, 2015 at 5:48 AM, Alexandre Rafalovitch
arafa...@gmail.com wrote:
Cool. This certainly answers my questions.
Thank you,
Alex.
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On
We have a lot of new features . It's a good time for a release
On Thu, May 21, 2015 at 8:40 PM, Erick Erickson erickerick...@gmail.com
wrote:
Don't get me wrong, good question to ask!
On Thu, May 21, 2015 at 5:48 AM, Alexandre Rafalovitch
arafa...@gmail.com wrote:
Cool. This certainly
Hi Upayavira,
Sorry for the delayed reply. I plan on cutting a branch on Thursday evening
and getting a candidate out for vote sometime Monday/Tuesday (if all goes
well).
How long do you think you need for getting the admin UI in?
P.S: All times are in PST.
On Mon, May 18, 2015 at 12:30 PM,
Just to be clear the new AngularJS-based admin UI will _not_ be the
default for 5.2, the default in 5.2 will still be the current UI. The
hope is to get it out there for people to experiment with/provide
feedback on with an eye toward making it the default in 5.3. And add
some nifty new features
Actually, a Monday/Tuesday deadline is no bad thing. I'd be happy for
the admin UI to go out in 5.2 in the form it is now, although there
might be a further tweak or two that could make it by then.
Thanks!
On Wed, May 20, 2015, at 06:11 PM, Anshum Gupta wrote:
Hi Upayavira,
Sorry for the
On 21 May 2015 at 06:03, Erick Erickson erickerick...@gmail.com wrote:
Just to be clear the new AngularJS-based admin UI will _not_ be the
default for 5.2, the default in 5.2 will still be the current UI. The
hope is to get it out there for people to experiment with/provide
feedback on with an
Well, it's all experimental at this point, I have no reservations
about upgrading from Angular 1 to 2 between 5.2 and 5.3 so it's not
locked in to anything. That said, what are the compelling reasons to
go with Angular 2 that make it worth the effort? The argument that
it'll be more supported
My understanding was that it will be quite a bit of a pain to change.
They are rethinking the whole architecture. By the same token, there
might be quite a lot of Angular 1 momentum even after Angular 2 is
released.
To be clear, I am not really recommending or arguing anything. It's
not my area
This is really the first time the topic's come up. Let's rope in
Upayavira on the discussion, he's really doing the work.
Erick
On Wed, May 20, 2015 at 7:12 PM, Alexandre Rafalovitch
arafa...@gmail.com wrote:
My understanding was that it will be quite a bit of a pain to change.
They are
Hi,
Seems like there's enough features + improvements + fixes and it'd be good
to release a 5.2.
To name just a few, there's the new faceting API, rule-based replica
placement, Solr security framework, Solr streaming expressions, upgrade to
Jetty 9 and a lot of refactoring.
I'd like to cut a 5.2
I'm hoping that the angularJS admin UI (patched at SOLR-7558) will make
it into 5.2, so that we can get some serious user feedback. That
currently rests upon Erick's shoulders :-)
There's a few known issues in it that I'd like to resolve before 5.2 -
how long is planned between the branch and the
13 matches
Mail list logo
