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 <[email protected]> wrote:
> Don't get me wrong, good question to ask! > > On Thu, May 21, 2015 at 5:48 AM, Alexandre Rafalovitch > <[email protected]> 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 21 May 2015 at 17:58, Upayavira <[email protected]> wrote: > >> 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 advantage of > >> AngularJS to make that clearer. Thus, any migration to AngularJS 2.0 > >> should be simpler because of this work. > >> > >> The lines of Javascript has approximately halved in this new impl, which > >> should make it all-round easier to maintain, in whichever way we choose > >> to take it. > >> > >> Upayavira > >> > >> On Thu, May 21, 2015, at 03:12 AM, Alexandre Rafalovitch wrote: > >>> 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 of expertise. It just felt like there was a small pink > >>> elephant in a room and I wanted to ask what the position on it was > >>> from the people actually doing the work. Or be pointed at the > >>> discussion (e.g. JIRA) where that particular elephant has already been > >>> examined in details. > >>> > >>> Regards, > >>> Alex. > >>> ---- > >>> Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: > >>> http://www.solr-start.com/ > >>> > >>> > >>> On 21 May 2015 at 11:17, Erick Erickson <[email protected]> > wrote: > >>> > 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 going forward is taken as a given. Do you > have > >>> > any estimate how much of a pain it would be to change? > >>> > > >>> > On Wed, May 20, 2015 at 4:17 PM, Alexandre Rafalovitch > >>> > <[email protected]> wrote: > >>> >> On 21 May 2015 at 06:03, Erick Erickson <[email protected]> > 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 eye toward making it the default in 5.3. And > add > >>> >>> some nifty new features between now and 5.3 that would entice > people > >>> >>> to use it and thus generate feedback. > >>> >> > >>> >> I did not see this mentioned anywhere. Are the - significant - > changes > >>> >> in Angular 2 going to affect this new UI? Or do we lock in to the > >>> >> latest Angular 1 for a while? > >>> >> > >>> >> Regards, > >>> >> Alex. > >>> >> > >>> >> ---- > >>> >> Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: > >>> >> http://www.solr-start.com/ > >>> >> > >>> >> > --------------------------------------------------------------------- > >>> >> To unsubscribe, e-mail: [email protected] > >>> >> For additional commands, e-mail: [email protected] > >>> >> > >>> > > >>> > --------------------------------------------------------------------- > >>> > To unsubscribe, e-mail: [email protected] > >>> > For additional commands, e-mail: [email protected] > >>> > > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ----------------------------------------------------- Noble Paul
