v7 - What version of Angular will be targeted?

[Jason Prothero]

Any chance the version of angular can be upgraded to 1.2.1 or something?

What version is targeted for release?

Thanks,

Jason

[Sebastiaan Janssen]

1.1.5. The recent release (1.2.2) came too late for us to update. They don't seem to be applying SemVer either as there are breaking changes so we'll update when it feels appropriate.

--
You received this message because you are subscribed to the Google Groups "Umbraco development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to umbraco-dev...@googlegroups.com.
To post to this group, send email to umbra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/d25b5361-161d-47c1-ba71-dd6db44f9504%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Mikael Syska]

Hi,

Yes, they are breaking changes but also gives new features... but they should follow SemVer.

Please consider getting 1.2.x in the final release for 7.x or else we will be stuck on 1.1.x for a long time.

Might have missed the point of "when it feels appropriate" ... if not now ... then when?

mvh

Mikael Syska

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/CAE1%2BSNpJ72n%3DvsoJSKEkQWx-kn1F3PG3tA%2BXW%3D9Z6H%2BoJFxQ4w%40mail.gmail.com.

[Sebastiaan Janssen]

Mikael, we released a RC a few weeks ago and an RC means that we have a feature freeze which means bug fixes only. We're 2 days away from a final release so we can't just go and upgrade and hope for the best. 

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/CAJYT2XkG9yjYPxfsAWTXC_wfQmX1LhnJFtS2OS-wJqw3Wf1mNA%40mail.gmail.com.

[Mikael Syska]

Sebastiaan, I know that ... but a final was still first scheduled a few weeks before this new deadline in a few days ... this shows that it can be rescheduled when it makes sense. :-)

If people start using AngularJs in the backend, which I guess they will ... when will this breaking change then be released? Either way it will break stuff and as I see it, this will be the best point in time for getting 1.2.x in.

But I totally understand Umbraco's planned schedule.

So bottom line ... asked in a kind way. In what version can we except it to be updated to 1.2.x?

mvh

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/CAE1%2BSNp2D%3DR5-jege9jg9hb6rXKmzba_G_5CpRHE%2B7aXUa1KyA%40mail.gmail.com.

[Sebastiaan Janssen]

This is not the time and we're not going to delay our release for it. 

If we were to reschedule our release every time a dependency has a new version, we'd never release anything (remember, we very recently had releases of MVC 5, Web API 2, Json.Net 5.something..)

The (admittedly unsatisfying) answer is: we'll see when it makes sense for Umbraco. 

I'm sure we'll be able to help anybody who has built something against 7.0.0 to upgrade with us. Which, yes, this means we might introduce a change that's not backwards compatible in Umbraco. That said, a JS change is way less intrusive than a .NET change that just fails your entire website. So, in this (for us) uncharted territory, we might want to be a bit more aggressive then we are in our compiled code. 

Again: we'll see. We'll be asking for your opinions and objections along the way.

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/CAJYT2X%3DinsA5tH%2BVdG_Q0yVZXgt5sP42GZi%2BZvuiOnPFKUHgyQ%40mail.gmail.com.

[Mikael Syska]

Hi, comments below.

On Wed, Nov 20, 2013 at 12:01 AM, Sebastiaan Janssen <jan...@umbraco.dk> wrote:

This is not the time and we're not going to delay our release for it. 

If we were to reschedule our release every time a dependency has a new version, we'd never release anything (remember, we very recently had releases of MVC 5, Web API 2, Json.Net 5.something..)

Yes, thats kind of the next thing.

 

The (admittedly unsatisfying) answer is: we'll see when it makes sense for Umbraco. 

I'm sure we'll be able to help anybody who has built something against 7.0.0 to upgrade with us. Which, yes, this means we might introduce a change that's not backwards compatible in Umbraco. That said, a JS change is way less intrusive than a .NET change that just fails your entire website. So, in this (for us) uncharted territory, we might want to be a bit more aggressive then we are in our compiled code. 

Agreed.

 

Again: we'll see. We'll be asking for your opinions and objections along the way.

I would say as soon as possible ... I also foresee some change request when it's final and people start using it... 

But so far I love it. Keep up the good work.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/CAE1%2BSNqj-8KoBNtZR5pjh%3D2QxgTkKuupBJyfw2KGMn-QQH7Xhg%40mail.gmail.com.

[Niels Hartvig]

The question I'd love to ask is: "Why would you want AngularJS to be updated". Because of specific fixes or features? Or just for the idea of always running vNewest?

/n

[Mikael Syska]

Hi,

The reason I want it to be the lastest stable when umbraco is because 1.2.x have breaking changes compared to 1.1.x as Sebastiaan mentioned. I i'm sure the Angular team have a good reason for breaking stuff now than later, if it makes AngularJs better, faster and more stable.

There is no better point in time than updating it now so there won't be any breaking in the future. I also see the point that you guys want to get the final release out.

I haven't used AngularJs much yet, but I personally wont be looking into 1.1.x for new projects. I have seen things taken from the AngularUI project merged into 1.2.x

A speciel feature which is now in angular is the "ng-if" which came from angualrui. I'm sure there are loads of other new stuff and imporvement when I will start working with it in the next few month.

For the other .NET packages I don't really care ... no new stuff there as I see it ... 

Btw, you should change the Nuget package spec file to require MVC 4.0 since MVC5 support is not done yet, as I understand it from an issue on http://issues.umbraco.org/issue/U4-3560

mvh

Mikael Syska

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/3c33d448-05c9-4c56-9001-9d221c730f52%40googlegroups.com.

[drph...@gmail.com]

Maybe because 1.1.* is an unstable branch?

[Per Ploug]

Yeah its marked as unstable, but we have been running on this version for the past 4ish months, and it has been stable and fine for us - so do you really think that a brand new release - which has not been in many production sites, with such a long change-list will be more stable? 

It might be, but we dont know, and as they've already sent out 2 patch releases, I think we have not seen a mature 1.2 release yet - so on the day of releasing umbraco 7, I'm not changing away from something I know, to something I dont.

For breaking changes, yes there are breaking changes, but its on the application-level, like routing, and in the way that we manage modules and what files to load, they've changed this quite a bit 

- but for developers who are building property editors, or using umbraco's own services, you wont feel those breaking changes.

For ng-if - we have back-ported this, so its part of our application, so if you use ng-if it will work, and will be upgrade-able

And its not like we've been struggling with the poor amount of features in 1.1.x, its not like 1.2 is a revolution, because its not, its just a newer version, which to 9/10 developers working with property editors 

inside umbraco wont mean a thing.

/Per

[Jason Prothero]

Specifically, I'd like to be able to use the new ng-repeat-start and ng-repeat-end stuff.  Otherwise, I'm stuck creating a directive to do the same thing (probably in a un-optimal way).

Thanks,

Jason

[Mikael Syska]

Hi,

On Thu, Nov 21, 2013 at 11:25 AM, Per Ploug <pl...@umbraco.dk> wrote:

Yeah its marked as unstable, but we have been running on this version for the past 4ish months, and it has been stable and fine for us - so do you really think that a brand new release - which has not been in many production sites, with such a long change-list will be more stable? 

So has the 1.0.x ... stable but misses lots of features.

 

It might be, but we dont know, and as they've already sent out 2 patch releases, I think we have not seen a mature 1.2 release yet - so on the day of releasing umbraco 7, I'm not changing away from something I know, to something I dont.

Have they sent out patch releases other than 1.2.1?

But not to sound like a dick, but I don't think any would run a production site on Umbraco-7.0 ... same as they won't on 1.2.0 of angularjs.

 

For breaking changes, yes there are breaking changes, but its on the application-level, like routing, and in the way that we manage modules and what files to load, they've changed this quite a bit 

- but for developers who are building property editors, or using umbraco's own services, you wont feel those breaking changes.

Now thats a good reason now for putting this into 7.1 then.

 

For ng-if - we have back-ported this, so its part of our application, so if you use ng-if it will work, and will be upgrade-able

Good. 

And its not like we've been struggling with the poor amount of features in 1.1.x, its not like 1.2 is a revolution, because its not, its just a newer version, which to 9/10 developers working with property editors 

inside umbraco wont mean a thing.

You might be right.

Like i wrote in the first post ... I just don't want to see extensions/plugins for 7.0 break just because of this. You have the insights in umbraco and how it's used so a better chance to see if upgrading would potentially break stuff.

I will confident that you are doing the right thing. I will start do some more 7.x cracking.

/Per

mvh

Mikael Syska 

[Jason Prothero]

Would it be possible to add an upgrade to a version 1.2 in the v7 minor versions road map?

I seems like the 1.1.5 is listed in the unstable versions on the docs site.  (See the version selector in the upper left).

Thanks,

Jason

On Tuesday, 19 November 2013 13:23:08 UTC-8, Jason Prothero wrote:

[Per Ploug]

1.1.5 has been out and used for months, I wouldnt consider it unstable - but at the time, the only branch marked as stable was the 1.0.x one, which was missing alot of required featueres, the next stable one was 1.2 which was then delayed for 5 months. 

7.1 is the next planned, larger-ish release, which is likely the best time to upgrade, which also gives the 1.2 time to stabilise, think they've pushed out 4 patch releases already, so things are still maturing.

/Per

[Jason Prothero]

Yep, no problem.  I just run into little things that exist in the AngularJS docs (which show the latest stuff by default) and don't exist in the version that Umbraco 7 uses from time to time.  Its mostly just annoyance, but I imagine it will only continue to get worse.

I just wanted to push for it to be on the roadmap since I know you are figuring that out soonish.

Thanks,

Jason

[robert...@gmail.com]

Is there any word on the upgrade to angular 1.2/1.3?

It's been quite a while since 1.1.5 was state of the art. Or did I miss something and was the angular version already updated in the new umbraco version?

[Robert Foster]

Hi Robert,
There was some discussion in a thread about this some time ago on the Dev Google Group, don't remember the details, but the gist of it was this:

There will be no upgrade to 1.2+ for 7.x as it would result in breaking changes (to 3rd party custom datatypes/dashboards etc.) so the earliest we're likely to see a more recent version of AngularJs is probably going to be Umbraco 8 ... and who knows - they may choose to go with Angular vNext. (this was also discussed recently - possibly the Umbraco blog, can't remember).

Hope this helps...

Rob.

--
You received this message because you are subscribed to the Google Groups "Umbraco development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to umbraco-dev...@googlegroups.com.
To post to this group, send email to umbra...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/bd2fa1a8-bf7f-4619-b435-e7d25aa6ca34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This email message and any attachments are confidential and subject to copyright. If you are not the intended recipient, any use, interference with, disclosure or copying of the material, is prohibited and unauthorised. If you receive this email in error, please advise our offices on 03 5282 4246 and delete this email and any attachments immediately.

Thank you.

[Aaron Powell]

You're referring to this blog post - http://umbraco.com/follow-us/blog-archive/2014/11/4/umbraco-and-angular-20

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/HKNPR03MB4206AFB753F3B5557532138826A0%40HKNPR03MB420.apcprd03.prod.outlook.com.

[Robert Foster]

Yep, that would be the one... according to that blog entry, it's likely AngularJS will be used for Umbraco 7.5...

Robert Foster
Director, Development

Microsoft Certified Solutions Developer - Web Applications / Umbraco Certified Developer

0418 131 065 / 03 5282 4246 / rob...@digitalsmith.com.au



w digitalsmith.com.au / t @_digitalsmith_ / f craftingyourdigitalpresence
a 11 Haydn Street, Lara, Victoria, 3212

To view this discussion on the web visit https://groups.google.com/d/msgid/umbraco-dev/BLU402-EAS717A0E88B03EB4D4C5ACA5EE6A0%40phx.gbl.