] Going to be collecting community feedback on our Ivy for Libraries plans soon

If you want a change to land in the master branch, target master only, or split your PR.

Know how many other PRs conflict with a proposed change, measuring "churn" caused by a PR

Changes to v9 must be targeted to "master + patch". Changes to v8 will need merge assistance.

] great work over the last 6 months from team, collaborators, contributors. A huge thank you to everyone!

] Ivy adoption & ngcc - Libraries will be the biggest barrier to Ivy adoption / out of the box success. Tracking libraries and looking at configuration around common library issues and additional education.

Test harness infrastructure to create component tests, so you don't have to write your own selectors, etc that might break when we change Angular.

8.3 builds are faster because we downlevel from es2015 build, instead of doing two builds

Tracking and designing our build & CI processes to increase speed, build times will go up with more code, so we have to keep building smarter

Locking issues that are closed and inactive, sorry for the emails!

We will ngcc es2015 libraries, and then we will downlevel (instead of running ngcc on es5 libraries)

] ~32,000 developer survey results, developers cared most about runtime performance. Happiness and ease of updates both improved. Blog post under development

] We're trying to expand our support for top Angular contributors (called Collaborators) with mentorship

This change enables Miško to focus on deep technical issues and the future of Angular.

[AlexE] Don't copy 3rd party code into the angular/angular repository without appropriate licensing and documentation. README in the

[Stephen] If you are removing a public API symbol, make sure you include redirects to help angular.io users end up at the right place

Adding Windows CI so we know of breakages on buildkite (not CircleCI)

[Igor] reminder: Various ad-hoc documents and documents presented in the team meeting are not accessible to

Calendar invitation has the link to the survey, sent to team email alias

Also working on getting Angular Material dev app working. A handful of the simpler components are functional.

This initial testing step down to diagnosing the last few dozen issues

Does not apply to code compiled with the ng_module rule, only ts_library

the part of the commit history. Use the PR box for things related to

If changing a behavior, describe both the old and the new behaviors

Last bit will be getting i18n atop Ivy (just 2 PRs in review to go!)

Schematics & architect work so you can do ng whatever with --prod

Will be asking for more help from the rest of the team to work on integrations at Google and CLI

Enabling all tests in Ivy and have a tracking spreadsheet of all tests

Please Be Packed and Powered Down By: 7pm on Tuesday, 8/21

A GDE build a smaller replacement for Reflect Metadata polyfill (tho folks don't need it anymore in prod but you have to turn it off manually)

Several blog posts coming up - one on the Grab 'n Go loaner project

Rob & Hans went to TransUnion bringing them up to speed on all our best practices - much excitement around the CDK

But still we have some work done somehow… :) A few more releases around Web Component support and bug fixes.

Lazy loading strategy uses Rollup. Also have a Webpack version. Need to invest to get this working for the full solution.

Now have saucelabs builds working similar to how we do it in g3

No plans for next minor at this point

Want to get to the point where everything in Angular is lazy loadable

Alex Eagle is doing a great job with his Early Access Program & Support for companies who want to use Bazel.

Will land build for ext world in JIT mode coming soon (or has landed?)

Had ~2K attendees in our "Pushing Limits of the Web With Angular"

Getting good feedback from trainers on simplicity of the new treeshakable providers API

Several of us going to work with Google Cloud team on their architecture plans

With message that folks should open new issues and refer to this one if there's a regression

No, we want to do this with humans, not bots

Igor + Manu will process and bring to the next Monday meeting for actions

Have meetings with new enterprises every week with 100s of developers each

Also talking at We Are Developers in Vienna next week (Stephen)

Docs has a few issues. Most blocking things already merged and ready to go. Just nice to have stuff left.

Docs: Elements and tree-shakable providers on track for merge today. Needs some validation on Tour of Heroes to align with CLI generation - targeting Wednesday. Adding an 'Update' page for RC on Wednesday as well.

ng_package bazel rule needs update to work with Material (and probably others)

Meeting on the update story to agree on public path to get to 6

[igor] how to get breaking changes reviewed and merged - focus on minimal developer pain

[Igor] talk about features of V6 (why it is worth it even without Ivy)

Much excitement over our plans for Elements, Bazel, and ng update in particular

We are consolidating several sprints plannings into just Framework, Material and CLI

no meeting - holiday

Dogfooding the ABC project on road to helping other companies use Angular with Bazel

Have 3K results on main survey and 1K on extended survey (this is amazing)

Brad has details on how to give kudos (in cash!) to external contributors

Announced Angular Labs as label for stuff that is ready to test but whose API may change. Includes:

Want to make sure team members know it's critical to say when conduct is "not cool"

Make CLI fast in watch mode. Current tsc ~2sec. There's some bug where they recompute too much.

Adds new injector 'import' feature that lets you load services by stub/proxy that resolves at runtime when used

Could serve as lower-surface way to start in Angular by just creating reusable components as custom elements

Angular is currently good at consuming custom elements but there's no way to easily create them from Angular components

CLI: Just waiting on faster ngc to see if AOT will be default or optional

(not for prime-time, no expectations that this will be for real use)

Created as a service we hope gets integrated in other online editors (we don't want to compete)

Plan to later release as generic functionality for automated refactoring tasks for anyone

Plan is to use inside CLI first to reduce complexity and code size

Work is in progress, nearly done, but needs security review.

Higher level API for rehydrating a HTTP cache on the client base on data queried on the server using the low-level API

Low-level API providing a key-value store you set up on the server becomes available in client

Adding Lighthouse support to CLI so you know how you're doing

One use will be for folks to create minimal reproductions for Angular team to work on with bugs

Switching to make AOT be the only mode for many developers so they can test everything they used to use JIT mode for now in AOT

Seems like the team could use a name that's inclusive of the full set of products

Had a release for 4.2 with too many regressions for comfort

Product is very mature - bugs are either very small or very new/zany ideas

Getting more accessibility help from experts that will hit future releases

Using non-Angular libraries is still a pain we need to work on

Easy to orchestrate animations in parallel and in sequence across route changes

Every other question was "how do I upgrade from AngularJS to Angular?"

Docs plan - doing an overhaul over the next few months

Need a general means of code splitting for use beyond Router that works in CLI

Possibly want a universal bundle format and tools that know how to work on it

None of the tools are composable (they assume they're last) and none of them do everything we want

All versions will still be served, but we want to make sure folks use the best sub-version of their chosen version

Docs came up as a barrier for lots of folks. We need to simplify the learning journey.

Q2 OKRs approved, now planning for Q3 to get us to v5.0

Suggestion is not that we change any commitments, but focus on user impact of every change

Every change has potential to be breaking -- for example, folks may rely on bugs and fixing that bug may break folks.

Want to be clearer about what we incorporate into major vs minor releases

CLI received lots of positive responses as well - coordinating the releases was very well received

Now getting feedback from early adopters. Busy fixing a few bugs. Will want broader sets of folks giving feedback later.

Highlights for folks include improvement in speed, size, Service Worker support, packaging improvements, all with low to no cost upgrade.

New zone release this week to fix some other bits, but doesn't affect public API

Working on a plan to make better performance for apps on AngularJS and Angular through ngUpgrade by making zones smarter

Landed namespacing change so teams can have both v1 and v2 components in the same app

Can now create apps using Angular v4. This will be default when Angular goes to RC.

Visited some of our partners/customers and local community. Discussion of pain points and issues.

Stephen spoke at AngularMN meetup and GDG DevFest. Demo of upgrade for 2.6 (and how easy it is) won a lot of fans.

Currently deciding the details of how 'long' long will mean and what types of fixes.

For these folks, we want to create LTS for AngularJS and Angular so they can feel comfortable deciding on a release to use across their enterprise for a longer period than our release schedule.

Have been talking to many enterprises who don't have ability to upgrade as often as we make major releases.

We've made this change throughout everywhere we can find in docs, wiki, etc.

Last week blogged that we prefer 'Angular' for v2.x+ and 'AngularJS' for v1.x

Intention is that this becomes part of Angular CLI in March/April as part of the Angular v4 release

New process for design docs. Jules gave a quick overview of review process we'll be using moving forward to make doc sharing easier.

We're working on closure integration and tree shaking to further optimize compilation of angular code via closure.

Tobias gave an update on his improvements on the view engine for reducing generated code size. Tests in benchpress are looking good. Animations will also be more efficient as a result.

We'll have a beta branch after that similar to other angular projects.

Tight focus on performance, build time, rebuild time, and documentation for 1.0 release to support the next angular major release.

Localization for docs is very important. It was really helpful to have support from local engineering teams on translation at our events.

We have a lot of users in China! Rooms were packed for our talks (Angular was the second largest track at the conference). It was great to connect to local developers.

Participated in the Google Developer Day events in Beijing and Shanghai. Also ran local codelabs and meetups, organized by Developer PM in China Aaron Zhang. Kara gave her live-coding demo (and introduced it in Chinese).

AI: Naomi will reach out to ES2017 champions to see if we can help with the bugs.

We'd like to recommend folks go on the new ES2017 polyfil

There's a better feature set coming in ES2017. Polyfil for this is also buggy.

Missing features are particularly big in custom formats for dates and such

Our hope is that folks just refer to the current project as "Angular" rather than "Angular 4", "Angular 7", etc.

The "2" is no longer useful as SEMVER means we'll be upgrading our major version 2x / year

Much of team is in China or Japan at conferences this week

Spoke at ng-be about Angular 4 to help folks understand major releases are low-stress events -- blog post with details coming soon

Working on tooling to automate whatever breaking changes we can, even for obscure cases

We're skipping Angular 3.0 and going to Angular 4.0 so we can align core with router which is is already on 3.0.

We have a breaking change coming so we can get on TypeScript 2.x (d.ts file format isn't backwards compatible)

We've been talking about "Angular 2" for a long time, but since we'll be having 2 major versions per year this no longer makes sense.

New CLI would be a shell over this new toolkit

Existing projects with large scope needs what we have in the CLI but being called by a different tool chain

Talked about Cypress e2e testing framework - Julie/Igor will investigate more vs what we're doing with Selenium

Gave talk on how we think about building frameworks and influences on how we created Angular 2

Folks wonder if we're using shadowDOM and think that's why we're fast (it isn't)

Questions around Angular 3 and what this means (folks worry ng3 will be a big pain migrate - it won't)

Focusing on making Ionic apps faster as a first use case as it pulls in several third party libs

We're working with the Firefox team on convincing them to revert their block

This does not appear to be Angular related

PrimeNG looked very nice, but ended up on ngBootstrap as it works with AoT today

Can't get responses to our issues from any channel

Next will be to improve the developer experience and potentially make changes to the platform server

Moving the core platform node part to the angular/angular repo so it stays up to date with any ng2 changes

Agenda:

Agenda

Kicking off issue queue triage this week, Igor to send email to the team with components.

Beta-1 of angular 2.1, and 2.0.2, are current versions. Our next weekly release, 2.1 RC0, is planned for this Wednesday.

DevRel folks will be on planes for the rest of the year helping folks get going and/or be more successful with Angular 2

Pushing a release to NPM tonight with some fixes for folks to try out. Will be promoted to RC7 when we pass validation.

Repackaging ng2 core. Just upgrading to the latest version of TypeScript but have found errors and will consult with the TypeScript team.

. Getting working for internal projects and then will be done.

Bundling strategy: Rob has a proposal that needs approval, creating a github issue to describe it. Hoping to make a final call EOD Tuesday.

Deprecated API removal: We should do providers first as its own CL, since this is ready. Julie to push next. Julie is preparing a master CL with the final changes to remove API usage from internal users at Google. Will assess Tuesday EOD whether ready to send the last remaining changes out for approval. [Julie R]

G3 is in sync with master. We have 8 PRs pending waiting to merge into master, testing now. (9 including the new zone.js)

Peer dependencies issue between zone.js and angular versions. Need a decision on how to communicate or fix. [Igor, Rob]

Hotel deadline today for conferences. Talk to Jules if you got mail from her.

API documentation: Need to do a final review pass on all API docs to check on experimental/stable/deprecated status. Also need a plan for updating the plunkers or removing them.

NgModules is complete in master. This is the last piece of the core API.

removes all deprecated APIs (planned: at least 1 week from RC5) and we assess I18N and Forms API and Animations for final.

No further breaking changes in Core before 2.1. New features in animations, I18N, and Forms only. Bugfixes OK.

No further breaking changes in Router, Forms, and I18N before 2.1.

CLI - need to determine what will be done on timeline for final.

We are now working out details of lifecycle hooks and testing API for NgModules

The core PRs for the proposal (from last week) are in master

We'll have 1.1 released by the end of this week.

Open issues - for discussion via the shared @NgModules doc. Please add them at the bottom or in Docs Comments.

will soon be ready to merge into master so folks can validate against it.

lifecycle callbacks - should @NgModules have a lifecycle hook at launch? (eg. create and destroy the module, create and destroy root component, router initialization as a case study)

No RC5 this week. Focus is on proving out @NgModules in master.

No RC5 this week as we're validating some new bits.

Working to validate the current implementation this week against Ionic, Periscope, Ames, and other apps and libraries we maintain.

The old way will be deprecated for a migration period.

Offline compiler - Material team got app working together. Some difficulties and bugs to handle. Two biggest pain points are CLI not playing well and lack of docs. Cookbook is in the works.

Docs - API docs now have tags that show which are stable/unstable. App modules and testing updates in the works as well as Router and Offline Compiler.

Forms - updateValue going into RC5, reset going in later, more features coming. As of RC5, no forms are included by default. Developers will specify the ones they want at bootstrap. Good time to move to the new forms!

I18n - Last issue is that we're not yet generating valid xmb files. Now fixing and will be in an upcoming release. Will discsuss docs plan next.

Router - Now v1 feature complete. Lazy loading, guards, etc. works. Release will come after RC5. More docs in the works to help with adoption.

CLI - Adding WebPack under the hood, support Offline Compiler, blueprints with app module support and new bootstrapping code, and upgrade story to get folks from ng2 vN to ng2 vN+1.

RC4 Milestone - Meeting Tuesday to review status.

Deep-dive on design and ergonomics this week. Will discuss at the next team meeting.

RC2 is released into the world, along with alpha router update, animations, CLI update, and new forms.

Some good issues filed on new APIs, working through these now

work this week (our GitHub custom triage app that integrates all aspects of Angular 2). Currently adding features that exercise:

Opt-in to new changes possible in RC2 once this last PR lands

We'll need more tooling to support other approaches. Still in consideration but not for RC2

From here to final: RC2 is unblocked, RC3 will focus on stability and closing out few remaining issues in the roadmap

Igor needs help on the v1 sync to internal. Alex E volunteers as tribute.

It’s fixed now by rollback. Pete is working on root cause so it doesn’t happen again.

We pushed a commit that broke the docs site because of flakiness on the CI server

No-meeting week in our product area, but adding some notes as folks have asked…

Will release as soon as we can resolve these.

Ran into issues in several places and needed to back-out some changes to get it working.

Goal is making it possible for teams with Angular 2 TypeScript projects to use the Template Compiler plus tree shaking to make much smaller/faster deployment builds.

Cleanup on API docs coming together (several private APIs are public when they shouldn't be).

Externally usable support for the template compiler in the next week or so.

Animations landing in core this week. Docs coming with this as well.

Have been getting on top of the PRs

. Was generally very good and Angular 2 showed off spectacularly in the performance numbers.

Appears that video for Cross Platform Angular 2 by Jules and Kara was lost. Big bummer, but was standing room only in the tent.

talk went spectacularly. Rob & Alex showed off our end-to-end solution for PWAs. Nearly 7K views on YouTube already.

Critical bit is in getting template compiler and tree-shaking (Rollup.js or jscompiler) working in the Angular CLI

Incorporating feedback from many folks on the latest changes in the release candidate

Next functionality will be on replacing inline-styles with classes and key-frames

Will resolve the plan for internal user sync mid-week when full team is back in office.

There have been some out-of-order SHAs merged in, which complicates the sync.

Martin is caretaker, but in an unfavourable time zone. Chuck J is the caretaker from Wednesday.

I/O is Wednesday next week, if we want an RC before then.

Web workers: need to be updated to repackaging. Igor to look into effort / tasks to complete this.

We can build the app, but tree-shaking via Rollup.js is not working properly

Now trying to consume them from a real app to test tree shaking

New router core works, end to end should work by end of the week

Working on an upgrade path to take folks from one angular release to the next (or any number of future releases)

John Papa made several suggestions that we'll address in the next few days

Will be creating Cookbook Recipes in the docs for folks to build their own

Will be adding tags to docs to indicate STABLE vs PREVIEW release status

Have landed changes to API doc styles that make them easier to navigate and use

Hooking up unit tests with ngZone so we can wait for components to stabilize before we continue in the tests

Have fixes for test component builder that will hit the next release (not today's)

Have template caching for tests so you can use fakeAsync with external templates

Have new async and fakeAsync test wrappers that handle errors much better -- all external folks should be using this now

Did not release last week as we're working through the new compiler changes

Tobias now working on Change #2 that will allow more dead code elimination. May be code complete this week.

We believe we can do better using jscompiler...working on this now.

Change #1 for offline compile is in MASTER (see last week for details). Coming in this week's release.

Will have app and build path that checks all boxes for Progressive Web Apps by end of this week

We will provide tooling (npm module for WebPack, etc.) for our component authors.

Writing up the design doc today and will share with component author teams. If you're not one of [Material | Kendo | Bootstrap | Wijmo | Prime Faces] and plan to publish component libaries, please reach out to @bradlygreen on Twitter.

The Angular CLI will be able to build with these inputs and build the right optimal version for developer deployments.

We'll request that component authors (Material, Kendo, Bootstrap, Wijmo, Prime Faces, etc.) publish ES6 plus generated metatdata files for developers to make minimal bundles.

http/2 won't have the performance needed for a while now, so users will need to generate minimal deployment compiles on their own

Now that we have a real path to payload reduction, we have other options.

We'd been assuming folks would have to use bundles to deploy apps.

There are many old repos under angular that we'll be deleting if they haven't had recent activity.

We've recently reduced owners for our GitHub repo to just our tech leads. Let us know if you're broken for any reason.

Also just need to make this go faster :)

Maybe need to do a blog post? Add more info to CONTRIBUTING.md?

It's invisible to external folks when their PR needs testing against all the Google apps -- this can take some time to resolve

Folks are unhappy with how long it takes to get their PRs in

The way we bootstrap host views is changing so that we can do tree shaking and eliminate dead code in final builds.

Much of core (compiler, template expressions, dependency injection, change detection) is moving to a code-generation build step. This improves performance yet again and lets developers drop much of the framework's size when deploying.

Two changes in the works, the rest is bug fixes and minor improvements.

Has a plan with 4 milestones to get to an Early Access edition

Minko Gechev is building a linter tool to give real time feedback to developers to help them follow the style guide. Integrating with Language Services so developers can get this help on command line and in IDEs.

Creating service to provide intellisense for Angular templates. Metadata extraction done. Many more steps required to get it to editors. Chuck has a hacked-up version that uses Angular compiler infrastructure to show errors that we produce in the IDE.

Working towards first release of this Chrome dev tool for helping explore/debug Angular 2 apps. Has many neat features like visualization of components, DI, and routes in one integrated graph.

Currently implementing the style guide into our blueprints. Will integrate offline compilation next.

Working on integration with other developer workflow infrastructure this quarter to complete the full picture.

Will have a mobile.angular.io sub-site to help folks get going

Well under way to show this via a GitHub management app

Goal is to make it easy for developers to create Progressive Web Apps on Angular 2

Will visit tomorrow to chat about a11y and will give a talk on a11y the Mountain View meetup

Angular CLI - Hans working on a design doc for tooling support on migrating to the next version.

Evan and Rado gave two talks on how we're making TypeScript work with our existing Closure compiler

The canActivate API has been hard as it can't be injected. Moving this to the parent so it can prevent lazy loading of code and you get full access to the injector.

Are simplifying aux routes and making them just routes. They will behave in the same way. The default route just has a blank name.

Will probably drop 'name' and just have URLs so we can automate lazy loading

Now highlights which elements were affected in the last rendering/data update

Jeff Cross will look at this in the next caretaker and send backfill features

Seems to be some kinds of bugs in the CHANGELOG script

Last week we shipped three things (router, views and zones) that weren't in the changelog

Igor bringing folks from Angular team and community together to resolve questions around best practices

There are some documentation issues that will solve many things

There are some critical issues, but not too many

Need other googler to help do the syncs

Should also provide consistency across projects so folks can immediately know where to look when they come to a new project/job using angular 2

We want to do much better in angular 2 with a set of guidelines that helps folks structure their apps in a way that scales from starter to giant projects

We had not seen large projects built with angular at that point and this set the tone for mistakes many years later in projects around the world

We'll have office hours for migrating from STABLE to STABLE+1 twice a year.

HEAD will be only for a small whitelist of folks who want to be on the edge

Have a strategy and plan where we'll have STABLE and HEAD for ng1 and ng2

Will be down to 1 version of ng1 at end of the month

Will meet to talk about building a single visualization with ability to turn on/off components, routes, DI on the same view (Igor Minar with set up)

Now using new API from Angular 2 (beta 8) to publish changes rather than using mutation observers and have gotten much greater performance

that's green in JS-land. Need to get it green in Dart-land. Should be a week or two before it can go in.

Reader that reads with the TypeScript ASTs and will let folks get this info without running Angular (ng-lint, etc.) - should be done this week

Metadata writer for files with d.ts files - green just needs to be merged

Has some bits but needs Chuck to finish before doing the rest

May be possible to use Hammer -- will chat with Misko to talk more

For Material 2, we're thinking we may write our own

Researching scoped packages to see if this is the right path

If someone is using all of our components, they should do it the same way

Con: The '@' symbol looks strange in imports and may not work for some

Pro: We own a namespace that nobody can name-squat on our package names

Folks seem to have heard our messages and have less worry and FUD about upgrading

All talks were very well attended and received much Twitter love afterwards

and give him feedback as it contains our core messages for the year.

(Google internal) Teaching in NYC this week, end of the month in SEA, April in MTV, May in NYC and LON in June

Router - now a guide for using the new router on Angular 1

Will have fork(), run() and wrap(). Errors will be forwarded to the global error handler.

Node folks are wary of things that looked like the domains feature they did so we're backing away from this for now

If they accept, Angular 2 in ES6 will be on par with TypeScript experience

Have several PRs on the way to improve several situations

There are several easy to identify cases when we analyze templates to identify cycles in change detection -- if you query for a child and bind to it, it creates a cycle. Non-obvious, but easy to catch and will be helpful to show errors.

Plan to publish these as a milestone on github so external folks can track

Needs more ability of folks who can sync to google (currently only 3 folks can do it)

Combine sync role with other Angular team caretaker to expand total pool of folks who can release

Goal would be that perf numbers can be compared within a batch

Travis is possibly good enough, at least for now

Biggest issue is creating an environment where others can take the benchmarks and reproduce the results

Jeff to do one on our vision around Mobile

Editable tree view is alpha, but coming along nicely (needs PR from Tobias - merging this week)

Dependencies have click-through that shows all other components that have the same dependency

Ward: Would be nice to have a feedback mechanism integrated into the tool as well

Alex: Would be nice to click on a component and trigger an event AND be able to see who subscribes to events

Rob: Would love you to reach out to Pascal Precht to integrate visual change detection

Tobias: Would be nice to be able to jump to instance of the provider

Planning on a test-jail process to rehabilitate them out of the main build

Problem is that it's hard to make it through the merge queue

Need to have a way to prioritize PRs for merging

Planning on publishing a milestone containing the burn-down for Angular 2 final by end of this week

There will be incremental changes, but no dramatic breaking changes

We're behind, but are working on merging the backlog this week

Last week we were out for part of it

How we're doing (based on analyzing the google crawl of the internet):

Is static, but our CSS parser lets us do choreography atop it

No need for getComputedStyle that we do in ng1 animations

Will talk to Marc to see how we can map this to React Native

Tobias: Would be interested in creating an explicit grammar for IDEs and other tools

We've set up both Angular and Angular+Hello World sizes with various bundling strategies to track progress

and see if there are items you'd like to take on

spikes in interest in Angular 2 around bigger events like ng-conf and Angular Connect the growth and interest is steadily growing and sustaining even after these events.

So far going very well with no real issues

Meeting with Drupal team later this week to find out what's most important to do next

It's early days, but we are making good progress thanks to volunteers from the community.

Working on a new approach that uses the Angular compiler as well

Next steps are to port the prototype to the plugin API

Working with TS team on a plugin API for this so others can do this as well

Goal is to give anyone building an editor/IDE Angular completions/error checking for free when using tsd

Moving HTTP out of the core repo (thanks to tool from the Dart team!)

Easier to maintain and build tooling around issues if this is a separate repo

Marc: Next, I'll be building some high level components and extensions to see the developer experience there.

Brad: It's also fine for this to be a differentiating feature between the two offerings.

Tobias: React Native folks have said they specifically don't want to go down this path for performance reasons. We might do some benchmarking to check it out.

Igor: Would it be possible to create a generic bridge like NativeScript has?

Marc: One thing is that not every UI component has a bridge. You will likely need to wrap with native code for things.

Marc: I just got a Mac and can do HelloWorld. The rest shouldn't be a problem. I don't really know the rest you'd need to do on iOS. Needs more investigation.

Marc: Certainly needs more tests. I'd want to see many higher level components with TypeScript types, etc.

Brad: What does it need to be even better?

Marc: I've tried it, but not sure if it doesn't work on Android or it just doesn't work. Needs further investigation. But with the rAF feature you can do multiple concurrent animations and it seems quite good.

Did a crazy demo where he put the ToDoMVC app into many bouncing balls in the screen - they all remained responsive

React Native exposes events that you'd get on a mobile browser which means that you can use tap, swipe, multi-touch like pinch, pan, or rotate

Brought this all together with the ToDo MVC and uses local storage

Support for the new i18n and Animations are coming as well, but we need to do work on the timeline.

The new Component Router will be going out this week for ng1.

There will likely be other tooling we create.

Next week, we have a be ng1 user where we're helping them do the upgrade to ng2. Also doing this with Shopping Express here at Google.

Most of the work will be in supporting folks in migration to Angular 2.

New Angular 2 releases should come out each Wednesday as well.

We have many issues and pull requests that we need to address.

Until then, there will be manual work to do things the same way

Most of the team will be at AngularConnect

Next phase will be for dynamic scenarios like gender and pluralization

First working on static messages - current work is on extracting static messages in the next two weeks

Working to make lazy loading / code splitting work with Component Router to make it free or nearly free based on your routes

Main feature is the component helper that lets folks build apps in the Angular 2 style and use the Component Router

Will do 1.5.0 final the following week or a week later if big issues

The next areas of ngAnimate will be un blocked once the parser is in

Plan is to do weekly releases from here to final

Performance should be obviously fast and map very close to what you'd write by hand

Goal is to automate all our processes through the robot on Slack/GitHub

Some is still left and should get done in the coming months

Igor and others created doc on cleanup projects we've always wanted to do

Leaning towards Hubot given less code required, direct integration with GitHub, and team familiarity with JS vs Ruby

Want to have this for Angular 2 as well, and even upgrade feature set

Cannot be an ad-hoc task, cannot be something done while traveling

Need to ensure that folks on rotation are in MTV

Angular should be very small for small apps and pay only for what you use for larger apps

Goal is to get Angular 2 Hello World app in under 10K payload size this year

Plan is for us to help more on bits we care about in Decorators

Generates less code than we previously did with the offline compilation so very large apps can scale better. Small apps will pay less.

Debugging should get better as you an now set breakpoints where divs are created. Could even create breakpoints in HTML templates.

Results will be easy to show via generated code as it looks like what one would write by hand.

Now planning to generate dependency injection as well. Further reduces payload size and improves performance.

Soon landing offline compilation to further improve startup time and reduce payload (don't need to ship the compiler with this)

But what about when you don't know you need to know new decisions?

Part of it is to be aggressive when you need attention

We want remote folks to be at the same level as others in the office

Tobias: I think what's really missing is the bits in the daily standup meeting.

Jeff: It's better for documenting rationale rather than discussion. Slack is for the discussion.

Igor: It's hard with the many opinions that can occur on GitHub

Jeff: GitHub is often better than Slack as it withstands time better than Slack

Julie: would like to see Slack used more aggressively

CSS classes will now just be used for styling. Animation metadata will be specified separately and can be part of the Component (inline or separate file)

Can be slow when you have lots of style sheets - currently drives folks to JS-animations

is almost ready - we are working on tooling to migrate existing templates

angular universal and service workers are at the top of the list

we will soon start working on deamon that will expose all statically analyzable info to IDEs and other tooling

when creating apis, think - can we statically analyze the code (imperative+declarative) and understand it? If not, tooling will struggle.

priority is on adding more integrations (karma, protractor, router, etc) and only then look at the long term plan for overall architecture (ember-cli, etc)

Ciro (GDE) and other volunteers have picked up some tasks and are making good progress.

Update: Going with 'ng' prefix on APIs to avoid collisions over using ES6 symbols for now. Decision based on simplicity over ultimate correctness given unavailability of symbols in other compile-to-JS languages.

Wrestling with the options for how to avoid name collisions

RxJS size reduction: Down to only adding 6KB. Want to go lower. Talking with TypeScript and RxJS team about further options.

Router docs: Ward is close on Angular 2 version. Needs Brian to review. Pete will start helping on Angular 1 version.

Router binding from host to child: PR ready to go when test for aux route completes.

Per-commit sync: Has flaky tests to deal with. Plan is to ignore flakes and have folks fast fix.

Parser: Vic has the PR ready -- merging in the next few hours.

igor will review the internal owners file to avoid collisions like we ran into this week.

we are back to the new normal. when a PR is ready to merge, add the "merge" label.

Agenda:

Need to worry about IDEs. Integrating with our compiler would make this work.

Victor would like to make it more generic so it can handle more cases of parsing many styles of templates

Having it for the Beta would be desirable

This binding transformation would let us hook into how change detection builds up data structures and modifies them

If you want to write a link in routing you have to write an array of strings+objects

Agenda:

We’ll have a set of improvement tasks that you’ll do instead of your regular work

All work should be happening in the beta-00 milestone (if you're working on something else, clarify)

Agenda:

Other bits will come ASAP, but not required for beta

In the bomb-run for AngularConnect. Getting in last bits folks need for demos.

After alpha-41, no more high-risk changes to MASTER until after AngularConnect

If you're not sure whether it's ok to check something in, please err on the side of caution and ping Igor to double-check

Building infrastructure to push ng2 to npm (and likely code.angularjs.org) on every green SHA

More details on the extra work that will need to happen at https://github.com/alexeagle/angular2-distro/blob/master/README.md

Also eliminates much work from our release process as we don’t need to generate them or push typings to DefinitelyTyped repo.

This will get everything set up without having to additionally configure IDE

Currently, there’s extra work to get all the typings files (from DefinitelyTyped) and linked in the right places for all editors and tools to understand them

Planning to generate a commonjs bundle so folks can much more easily use Webpack

. No breaking changes after that date. [Naomi to let presenters and docs know]

Work on sync to google internal in parallel. Rado is sync master. Tobias will pair. Priority for internal users is to get the compiler changes in.

Can we cut an alpha-39 by Wednesday - bugfix only to unblock docs? Plan on alpha-40 for Friday will contain the

We accrued a backlog by handing off work from week to week. In future, if we can't sync at the end of a week, declare a team P0 until it is resolved. This blocks handoff.

We are down to the last 20 issues to clear. Rado and Jeff to sync after the meeting and determine whether to escalate to internal teams for P0 help getting to the bottom of this.

Jeff broke the backlog sync of 250+ commits out into 1) rename and 2) other stuff, grouping into smaller chunks.

Once we are back in sync (not 250+ commits behind), or if we have the ability to deprecate, it may be reasonable to ask the Google owner of a breaking change to make the fix for users inside Google as a CL.

Some way of marking things as deprecated might help with the sync. Needs discussion. Rob prototyped a decorator that we can use to mark things as deprecated. Would this be helpful to submit as a PR? Adding decorators has a runtime impact for TypeScript. A comment would be simpler and also show up in documentation.

Currently, we provide a changelog, but it's a lot for an end-user to digest. Our commit messages could be more focused on end-users. Many breaking change messages in our changelog are not actionable (not clear to the user what they should to in response to this change). Jules is also open to providing a curated update per release later in the year.

Customers (internal and external) are asking for more detail on what has changed between versions.

Triage of Issues Status: We are 100+ issues behind for triage. Need a more scalable process. Revisit with Misko.

Status of DevDocs/API and where we need help

Brian is working on examples with the new tooling from Jay and Ward. Brian to update the API guide with instructions. This is similar to how it works in Angular 1, examples are separate files that can be tested. Not yet possible to provide as an interactive example, but on the road map.

Cheatsheet - Naomi would like to finalise this week so we can work on design. Victor and Misko needed to review.

Grading of Q3 2015 Quarterly Goals, and new goals for Q4 and overall 2016 (draft)

We may move from es6shim to core.js for ES6 bits (As do TypeScript & Babel)

After much hard work, it is gone from our codebase

Originally, we used Traceur to transpile from AtScript (now TypeScript) to JS & Dart

Came out with a list of issues we should process this week

still many issues around how we present content we create content (creating links, function signatures, etc.)

Several of the first concept guides will hit then as well

How will we test changes in a real UI as we go?

; copy links into content; later we will single-click link to the CodePen example

Blog post is coming. Brad will write it and introduce Jules to the folks involved.

We'll deprecate the old site and direct folks to it. All the content still lives in the github repository.

Handing off curation and ownership of the Angular showpiece site to community-run madewith.angular.com. It's more current, and has good momentum.

Blog post will be out next week with the results.

Beyond that, what are the critical overall visionary goals for angular?

Set up a team meeting for next week to think through: what are the clear tasks we want to prioritize to achieve user happiness by beta? [naomi]

The importance of focus on "the first 20 min" for a new developer

Need feedback from external contributors on what they need to be successful

Need to document things we shouldn’t do in TS (top-level execution blocks, const semantics, etc.)

Need to add this to our quarterly goals

Need conditional compilation (proposal coming) to get the code looking idiomatic for both language

Might be the right solution to let folks contribute in either TypeScript or Dart and have core team members do the porting

Going to add tests on AngularJS to catch more of the regressions

Updated all API doc source to match these conventions. This was the major breaking change. Will be pushed to the API docs on angular.io soon.

We still have Observable/Rx changes that we know are coming

Want to get to “no more breaking changes in core” very soon

to make sure we stay on top of it

Can now bootstrap Angular 2 inside Angular 1. Next step is to do the other way around. Will then work on transclusion and injection.

More sections specced out than we have authors for. Need help in the next 2 weeks. Specifically, these sections are outlined but still need owners:

Jeff aligning publishing with NPM and breaking Angular 2 into smaller sets. Have some remaining bootstrap and Dart issues to work through.

Have been working with Ward Bell on our testing story...many issues we’ve worked through. Have filed many issues related to this so we can make this better

Goal is to have Closure compiler be able to consume output

Proposing that we support both ngContent and add ngSlot to support Shadow DOM for folks who want it.

. Needs discussion after the meeting so we can decide what the best approach is.

We should be easing the burden of contributors who aren’t familiar with the dart build process

Results of running both tsMinify and uglify against ts2Dart sample result in 56K vs original 72K (also uglified) for a 22% space savings!

Offline compiler will also find errors and report them to command line or IDEs

Means production version of Angular could not ship the compiler code and become much smaller

Sub-teams will use journeys as a means of communicating what’s being worked on weekly/quarterly

Igor and others on the team have organized many “user journeys” describing how we expect users to interact with Angular 2.

Our team is big, we should have some more focused sub-teams.

Brad to publish first list of who is in which team

Misko will do the work to make zone.js issues show up in core dashboard

May spend a few days with Amadaeus in France the following week

Need to create topic list to get to who we’ll need

Known breaking changes for Angular 2 Beta are now on hotlist (Pipes is the last big bit)

Matias and Rob think they THE have the core idea for ngAnimate next gen

want to seamlessly define some animations as JS as well

Plan is to drive this from an animations.json file in the development project

Solving these requires that we drive via metadata instead of CSS

CSS no just has to specify end states, not how transitions work

Want to have several weeks of no breaking changes before beta

Will have full core team focus on this after breaking hotlist done - thinking September

Currently have a group working on infrastructure to generate docs with tests for ES5, TypeScript, and Dart

support - would like folks to start using it and give feedback on what is missing - Ionic team will start

Low hanging fruit will be replacing Rx 2 with RxNext with few combinators or completely unbundling it

Need to document the magic incantations that the CLI does for folks who need to do things themselves

Want to have a one-click experience for developers to install all necessary tools and configure build process through the CLI

so we can tell that the build has gotten slower/flakier and fix.

Alex will add this to COMMITTERS.md and merge these with TRIAGE and LABELS

Push a branch named 'presubmit-SOMETHING' where SOMETHING is anything unique. Recommend something like 'GITHUBUSERNAME-SUBMITTOPIC' so the result would be like 'presubmit-bradlygreen-supercoolthing'.

New process is that you should not push to master

Now plan is that we let developers mix and match components to allow incremental upgrade

Top priority this week are to get pieces we need to test examples in dev guide as part of release

Example did image effects and demonstrated the frame rate remaining at 60fps while doing the image processing

We may also break the build when two green PRs produce a logical collision.

As of last week, we changed our tests to remove default tests against dart on every PR (although we test before commit to master). We only run these tests when the PR is merged to master. This is a problem when issues

OK to check in late Friday commits since anyone can git revert if stuck.

to undo the prior commit(s). File an issue and follow up with the PR owner to make sure it is not dropped later.

If master is red, and the owner of the PR can't quickly unblock you (e.g. on a late Friday commit) do a

For any PR you want to merge, check to see if master is green.

We should set up a submit queue that runs all tests and pushes when green. [Misko]

Keeping the build time fast makes development easier. We need continuous performance tracking for our build so that when we check in a change, we can tell if it's substantially increasing the build time. Alex E has a PR to add this to our dashboard.

Externally, you can see where the latest internal sync is: [

per-SHA sync is still an unsolved problem. Alex E has been working on some dashboards to make the gap between github and google-internal more visible, and make it easier to track which SHA has broken internal tests.

Animations status - compatibility issues with angular material due to animations in 1.4 are resolved. some ongoing bug fixes last week.

DI status - one more round of renaming is coming in DI per early adopter feedback. breaking change but easy fixes in alpha-34.

closing out our 0.10.1 release for material. first look at datepicker will be available in master later this week, right after 0.10.1 closes.

CommonJS/SystemJS as a path for removing Traceur still unresolved. Alex and Ian to dig into this later in the week (after sync is handed off to Yegor)

We now generate types with dgeni and get them posted to definitely typed.

use of typescript and annotations in angular 1 (with an angular 2 code style) is close.

release blocked on one commit that’s breaking almost all internal targets. Lucas M is figuring out the best solution to get that unstuck.

Every P0 should have someone to pair with the reporter. If the most expert person on the team is heavily loaded, someone else on the team must own.

Action: follow up with internal user to make latency check a part of TAP tests. (is this feasible? too slow?) [Martin]

Benchmarks that caught the issue were internal, so not caught by Travis CI.

Sync on Friday was blocked due to a breaking change, so this needs to wait until sync is unblocked. Should be landing tomorrow or Wednesday.

Note to the team: please take care when writing commit messages. they're important to the changelog and sync process.

How to better communicate breaking changes to internal users on daily sync? [Alex to look into automation for how we can parse existing commit messages] Risk: many commits are not breaking changes but aren't noted as such in the commit message. Sync master would need to update commit message in that case.

blueprint: Alex will be constraining tests internally so that we can manage them

Rado is syncmaster. Last sync was Thursday. Large breaking change on Friday. Working on fixing internal users, will sync later today/tomorrow.

Matias is working on longer-term plan for how we effectively test for animations. Will set up a chat with Tobias, Julie, to talk about how to use Protractor for it.

Meeting tomorrow afternoon to discuss. Core folks, please join if you have expertise/interest. Ping brian to get an invite.

Next steps are prototype code and more ideas of areas we must cover

Assign issues in the dashboard that have a milestone but are unassigned

Currently hard for folks to tell what we're doing

Our dashboard needs work so we can easily see all issues…

Some theories of how we move forward on modules as system.js has issues

There are a few remnants of Traceur in our codebase

Matias will work with Rob to bring these into Angular 1 this week

Still has some quirks. Want to make API surface smaller before beta.

This week want to improve error messages to be more useful to developers. Every exception should have context of which direction/component was implicated and how to solve.

Jeff and Victor completed work on Pipes. You can now provision them in a reasonable way.

New content project PR lets any renderer us content projection - and it will be very fast! :)

Assign issues in the dashboard that have a milestone but are

Jeff will take on some pipes stuff in addition to Http/Observables work, TBD with @vsavkin

Are there any issues in buganizer that haven't been filed in github yet?

Change Detection - work on Pipes is the next piece of this effort, underway now.

DI - Merged a number of changes last week -- midway through the process of unifying to a single stable DI implementation used by core. Should be done this week.

Router - Landed support for deep linking. Lifecycle hooks and routeparams are next. Pete added a d.ts file for router. Matias will use this in an example coming soon.

. Caitlin working on JSONP support for M31, Jeff working on simplifying Observable/Stream output and updating to RxJS Next

Http - Landed Dart support last week, with minor breaking changes (and a couple of regressions). Created prioritized backlog of remaining http work in

Zones is pushed out to M32; at risk since vicb not available to own. Would simplify test story for us.

A good way forward would be to investigate server-side solution with node. Needs an owner. Brian has background but is heavily loaded on router. Revisit next week.

is core but blocking progress on the router. Needs an owner.

This doesn’t mean we’re going to abandon the Router strategy where views are the boundaries for migration

Igor/Misko were working on Angular 1 APIs that let you get close to Angular 2 and vice versa

Maybe move the Mountain View meetup to bi-monthly? Next one in August.

Next step is to chat with React folks per our earlier conversation this year around collaborating on this

We do not need the DOM diff layer of React - we use a layer deeper where we send commands

Another (long term) outcome might be more collaboration between ReactNative and NativeScript

We may end up supporting both routes for native if there is good reason

We want to learn what we can from the good folks at React

Issues that seem to be slipping? (about 16, out of ~45 assigned)

Rado: 2363 (issue had multiple checkboxes but 4/5 were done. could this have been more granular? how to convey to folks following the issue?)

Jeff: a bunch of http-related issues from 27 (2442, 2417, 2416, 2415) - waiting on a master PR in need of final docs.

Will re-start on docs after we nail down rework of the features in mid-July.

Have a method for generating URLs, but need a better method in the near future

See linked doc, but summary is simpler than in Angular 1 with much more ability to do complex animations tied to your app states

Plan is for Router to hook into them as well

New process for milestones, setting meaningful dates for M10 and M11. A tour of the new dashboard.

If issues are not actionable, we'll just close it so we stay on top of the open issues

Problem: What to do when a milestone can't be closed because of a late-found internal issue on sync-to-Google

Need to change our alpha release process to run sync tests before an npm push. Also need a tagging process to clarify when the release candidate SHA is in verification for syn. [Rado to own figuring this out.]

We will rename the milestones "M10" "M11" to match alpha release numbers. At start-of-week, we'll have three open milestones: the "closing" milestone that is frozen to check against internal sync, the "current" milestone where most of the work is happening, and the "next" milestone that has tasks > 1 week.

WARNING: if you use not-authenticated, you can lock yourself out of github. Click the link and assign an API token. (We'll fix this.)

Need to review the backlog issues to get a hotlist of all TS/traceur related issues

is high priority, should try to resolve this one sooner (M10 if possible)

We're looking at doing this via what we call Render Services -- singletons injected via DI that do rendering on behalf of your Directive

Right now, there's no good way to wrap direct-DOM widgets (jQuery, etc.)

Added scenarios for overlays/dialog boxes which can now be modeled in routes

to aid with triage -- shows items that do not have the triaged properties

Misko will write up as our new process for triaging issues

For circular dependencies, we’ll help on this with tooling (TypeScript can catch it) and JS VMs. This will be noted in the spec for implementers to handle.

All this was presented in TC39 last week. Generally went well. No change in status -- just an update.

We were pushing for function expression support. Given this, symmetry would want function declaration support. Found solution for this by hoisting and executing at top.

Discussion was very easy. We have full support for our metadata use cases in the work stream.

Will announce this if there are community folks who want to take it over

Once typescriptification and build stability are in, router, decorators, custom render, and finalising the public api in the core (app injector, pipes, forms) are next in terms of urgency.

Brian and Matias will work with Igor on plug-ins for build improvements. File build issues under the "Build" milestone for angular 2 so we can find them.

Tobias will focus on completing the core/compiler and render conversion to TS. Julie will take over some of the testbed work from Tobias to help keep that unblocked.

We are partway in our typescriptification process. Having a mix of TS and non-TS code is making the build fragile and hard to update.

As soon as core/compiler and render are converted, we'll need more people to help with the remaining migration.

We would like to break out the doc examples from the dev guide and make them testable (similar to angularjs.org). Needs help -- Julie to look into this as low priority item.

dgeni now has its own config file that specifies which top level modules are to include in the docs. See

We could use dgeni to generate d.ts files [Alex E. to file an issue, Pete will work on it]

API doc generation from dgeni via TS parser is in a PR ready to go. Needs signoff from Naomi or Alex W.

Working on the Test Component Builder which has two parts: 1) a mechanism for testing components outside of an application, 2) accessing elements and Angular's information about them in views. [Julie, with help from Tobias]

Need to update all the docs before we can push the change. (Jeff will help with the dev guide update.)

This introduces namespacing (ng-for, ng-if, etc...) so all docs must be updated

which we think should move to M9. Naomi to follow up with Will and Matan.

Internal angular 2 hackathon was very useful in finding bugs/gaps in our angular 2 API.

May 11th, 2015

Too many rough edges, not ready for v1.4. Work with Brian and Matias to improve it.

Would be nice to get this into a working state.

Tried using it for a clang-format release, didn’t work at all for me, even with hand-editing dependencies package.json files, always errored out

May 4, 2015

We need a plan for how we get the downstream angular 1 version of (for example) the router docs from our single source. Igor will run with this.

If you are updating dev guide content please ping Naomi, Alex Wolfe, Rado so we can get you up to speed on the new templates. angular.io currently needs a manual push to web hosting, any of us three can do that.

Tagging changes are coming for angular.io -- Alex Wolfe is doing the update please ping him if you have any guides outstanding.

Alex Eagle will help with next step work on extracting and transpiling examples from a single TS source. We'll prioritize API doc inline examples first so that we can get to Dart API doc publishing sooner.

We will be moving angular.io dev guide and api doc generation into the angular/angular repository instead of angular/angular.io (

We will be removing Misko's initial dev guide .md files from the angular/angular repo once the last of these (templates) is migrated over.

As part of dev preview, note that releases now have changelog, API doc, and dev guide dependencies. Please check that all of these are up-to-date before an npm/pub release.

Brad, Igor (maybe Naomi) will be available to help review proposed talks.

Please make sure you have sent Pete your name if you're coming, and your talk proposal. See the doc he sent out directly.

There are only @Directives and @Components. @Decorators are @Directives, @Viewports are @Directives that ask for ViewContainerRef and ProtoViewRef, and @DynamicComponents are @Components without a @View.

Alex Eagle - all hands on deck this week core team updating to the current TS build. Need your help, please coordinate on what you are migrating to avoid duplication.

Angular Material 0.9 is complete and available on CDN and bower. Introduces Chips and Typography, improvements to Tabs, and polish.

Seems like a good idea, feedback is generally positive. Looking at making this happen.

April 27, 2015

What does dev preview mean? API docs up, router, changelogs for each version after.

Long-term solution? Can we support a modular build system for angular 2 that is separate from angular 1 and angular 2? Needs more discussion to figure out the long term solution. Ideally, using the new build process for angular 2. Igor will come up with a plan to discuss.

Short term solution: copy code over to angular/angular and generate docs out-of-band and fix them up. Will do code reviews as part of angular 2 codebase.

Router is currently in its own repository angular/router and in angular/angular. Where should discussion, issues, history be tracked?

Process for modules that are developed outside of angular/angular (e.g. router, i18n, animations) and how to integrate them with angular 2 and angular 1 build processes needs a plan.

Hoping to land the renaming change by Thursday. We need the router checked in first.

There will only be directives (former Decorator directives) and component directives (a directive with a shadow view).

We're working on how to deliver the typings based on doc public exports.

Dart build is slower than it should be. Yegor is following up with Dart team about a separate issue with dartanalyzer running multiple times.

Broccoli build should be very fast; if it isn't, please raise issues.

Dart and JS pipeline are coming via broccoli now. The commonjs path through which we run all our tests in node are using broccoli as well.

April 20, 2015

Just want to give folks time to test out the RC before declaring full release

No, this is not ready for folks outside Google to start working with - currently only possible with direct access to Angular team

Misko: Looks like the right direction, though probably needs more discussion around the API

Will also upgrade to take advantage of language features in ES6/7, TypeScript, Dart

Performance: Key feature will be to avoid unnecessary reflows and combine sets of elements that must animate together

April 13, 2015

We will need to solve this in the near term so the Angular build doesn’t get too long

Has issues with supporting this as separate repos as the TypeScript/Dart build as we’d have to replicate all that build infrastructure

Plan to have all code in Angular 2 and create version that works in Angular 1

Matias/Brian/Chirayu working on ways for Router, ngAnimate, and i18n to share code in Angular 1 and 2

Need to know what to call the directive

Let us know if there are known issues with this naming scheme!

April 6, 2015

What will I have to do about all the open source modules I rely on?

Why this new template syntax? Do I need to use all those special characters?

How does MVC map to the new structure in Angular 2?

If I want to use a new language option, what’s the best way to get started?

Do I have to use TypeScript or ES6? What’s the downside of just sticking to ES5?

Ex: Dart analyzer causes friction. With multiple languages and source maps as well.

Trees later in process can have more files than those previously

Some design decisions won’t scale inside Google, though it maps better to blaze (bazel) than does gulp

Mainstream usage only in ember-cli (and even then only used as a lib, not as a tool itself)

Some concepts don’t have names at all. Need to fix this so we can describe in docs.

March 30, 2015

Still need migration guide and look for folks with issues

Waiting on PR from Pawel on http parameter serialization which should land today or tomorrow

Have an ES5 building working now. Currently LARGE (100K). Needs minification help. Currently includes many dependencies like Rx which need attention.

Goal is to support other, non-Dom renderers like from WebWorkers, mobile native (a la NativeScript), and server-side rendering

Now splitting Angular 2 rendering so change detection, DI and Directives are separate from animation, templates and other rendering concerns

Will have a PR for Angular 2 in a week or two

Will move to Rx 3 soon as is available -- it’s aligned with ES7 standards work

Next meeting we’ll take a look at which conference we’ll be at in Q3/Q4/Q1

March 23, 2015

Not started planning on 1.5 -- will do this once 1.4 is released

If Animation goes in, may have another beta to give it bake time

This week, Victor will implement data driven forms. Plan to have a prototype this week. Next week, hopefully usable.

Working on a common style guide and method for generating ES5/6/TypeScript/Dart from the same content source

Goal is to help people get started with developer workflow / tool chain supporting ES5, ES6, TypeScript, Dart and various build tools

Can currently transpile Angular code base to Dart, but it is not yet correct Dart. Correct Dart coming soon! :)

will bring ideas on what we’ll implement to the current world to get input on direction

Current work on chips-ui, may be in demo state by end of the week

Intent is that we can run Angular in other rendering scenarios:

Will land the new renderer tomorrow, in master with tests by end of week

March 16, 2015

For discussion later today:

Which projects will we support during early alpha (i.e. no docs yet)? Candidates:

March 9, 2015

Migration from Angular 1 to Angular 2 seems to work for most

Planning will start after Angular 1.4 release in the next week or two

February 23

Jeff: ng-conf presentation prep. Angular 2 Http design fleshed out with Caitlin and Ben Lesh, good foundational design, needs more examples fleshed out. Doing some work on Benchpress and Benchmarks this week. Helping David East as needed for new site.

Brian: Worked through zone issues. Some open items on GIthub with zones to improve debugging, planning to publish release tomorrow addressing issues. Has been addressing feedback on Github about new router. Preparing for ng-conf.

Naomi: Working on Angular Material 0.8 release. Website reboot for ng-conf. Internal conference preparations. Worked with Misko on defining Angular2 milestones. Doing some issue and milestone cleanup on Angular2 repo.

Rado: Worked on DOM read/write queue. Built a big Angular2 application for ng-conf, found some bugs and fixed them. Helping bring others onboard with Angular2.

Chirayu: Working on gender and plural support for AngularJS 1.4. PR needs a little work, hoping to land this week.

Alex: working on AtScript format support internally. Working on interop between AtScript and Closure Compiler. Compiler plays well with DefinitelyTyped syntax for Closure Library.

Tobias: worked on benchpress, major bits in, google internal integration, fix perf-ci jenkins job to remove flakes, working on ios-driver support, and then releasing to npm soon. Preparation for ng-conf presentation.

Yegor: worked on benchpress for dart, got it working. Working on DOM adapter, researching offline DOM adapters for server-side template compiling.

Misko: getting ready to present at ng-conf, working with Victor on pipes design, collaborating with Matias on animation.

Matias: Animations in 1.4 landing this week. Working on Animations for 2.0. Planning to keep same code for AngularJS 1.5 and 2.0, similar approach to router. Probably a couple of weeks before prototype, end of March to have a foundation to build on during April and May.

Caitlin: working on making angular2 function in jsc. Some issues fixed, others need work. Focusing on bringing in upstream Traceur changes to Angular2. Also helping

February 8

Pawel: Working on equivalent of ng-class= for Angular2. Planning to refocus on AngularJS 1.4 until ng-conf.

Rado: View reuse done for Angular2. Much better performance. Working with David on his Angular2 ToDo app for tomorrow night's demonstration.

Chirayu: On i18n working on message extraction code. Figuring out how to have expressions inside message format. Getting this done for AngularJS 1.4.

Igor: Spending time on the new Router this week. Later will visit the NPM team to discuss making it better for client-side JavaScript.

Victor S.: Did core functionality to forms. Working on basic validations for forms. Looking for the most ergonomic API for developers now.

Alex: Fixed bugs in AtScript to Dart transpiler. Added unit tests. Working on ideas how we can work closer with the TypeScript team.

Yegor: Pushed Angular2 scrolling benchmark to master. Angular alpha is packaged for Dart. Working on automating the packaging. Now syncing to google. Met with Dart team to integrate our benchmarks with their performance test infrastructure. Should complete in a month or so.

Pete: Chasing small pull requests for Angular 1.4 release to get to final in the next week or so.

Misko: Working on some structural changes in A2. Making lazy-loading of templates work for Angular2 with VicB. Doing annotation/decorator syntax with Jonathan from Typescript team.

Matias: Refactor of ng-animate -- will fix all known bugs everywhere! :) Have a nearly complete API. Added feature to move elements between pages. Making work with routing. ng-animate will automagically work with routing. Will have demo next week.

Julie: Will be in MTV this Thursday. Will work on Angular2 testability API and thoughts on end-to-end testing together. Thinking of new way to hook into WebDriver through a proxy server to make development more streamlined.

Brian: Working with Lucas & Pete to get API docs together. Focused on ergonomics and polish so we can announce availability of the new Router for 1.x.

Talked to Dart folks re running our benchmarks. And they can, including nice graphs, ... Yegor knows details.

February 3

Agenda

Bringing them up to speed on Angular2 - will identify areas to contribute

We have the ToDo app done, but needs core help as it has much that is rough

Heading towards 0.8 with many more components (select, svg icons, menu, icon buttons, textfields, grid list, list controls) - will have an 0.8 release candidate by next week. [

Rewrite should be done in a few days and work for both Dart and JS

Working on vision doc on where to take Karma next

Mark Trossler (Googler) may take over Karma leadership from Vojta - final details to be sorted out

i18n - started work on the new js version of the parser, and running a weekly sync on project status

later focusing on moving the router into the ng 2 repo, and continuing to polish examples, docs, and remaining ergonomic issues

pairing with Pawel and Lucas on their feedback on the router in 1.x

Demos

Included Traceur so we can import AtScript and run it on the fly

David East will present it at next week's meetup here in MTV/SFO

Done with events. Will look nicer once Forms is done.

Has an issue with Zone.js not working with WebSockets. Fix in the works.

No way to chain animations or run in parallel - Want to add ability to have animation sequences

January 26

Welcome to Alex R., transferring from GreenTea team, joining Angular to work on RPC with Jeff

Had conversations with Ads and Cloud teams about components missing from the spec to address complex desktop needs

All folks on the MD project are here this week

Yesterday we met with a bunch of folks (Angular, V8, Closure Compiler, TypeScript, Chakra, and Flow teams) to talk about common needs around Types in JavaScript. Also had a good discussion about Annotations and Decorators. Lots in common.

The future will depend on how Angular2 is doing and how easy we can make migration. We'll need to sample to see.

We have an Angular 1.5 on the radar and are gathering ideas.

Angular2 will likely be a steeper migration and needs different thinking

What kind of a public timeline could we put together? We'd like folks to be able to comment on our plan.

Tobias in rewriting Benchpress to AtScript. Will need to improve webdriver/ieDriver to expose performance logs.

Jeff will start $http equivalent for Angular2 next week. Will sync with vicb on this.

January 12

Agenda:

Tracking historic results in Google BigQuery -- requires access, but we’re happy to give access to anyone who wants it. Not interesting for most as we’ll summarize results on every release.

Next step is to measure. Victor is prototyping this to check rough performance numbers.

It's possible that we can do the same trick for element injectors to make DI faster.

It's possible that we could drop the compiler and parser from production.

We can reduce the number of megamorphic calls from the # of elements to the # of views and should be much faster.

In Angular2, watches have to be known at compilation phase and we can pre-generate all of these.

After some analysis, we've made almost everything inline-able, but found that VMs can't optimize our call to the getters because they're megamorphic.

However, we think it should be faster.

We've made Angular2 two to three times faster than AngularJS 1.x for our Tree Benchmark

January 5

Agenda:

We'll make this the "new" benchpress (no new name needed).

Works in Chrome and (sort-of) on iOS today, via Appium. We'd like to explore ways of getting this to work on other browsers too. [

Not in master yet (will be later this week) but once checked in we'll be able to verify benchmarks on every Travis run.

Using WebDriver with Chrome, we can access the full timeline via Chrome's Remote Debugging Protocol (exposed via ChromeDriver,

We tried this once before. It's a good idea, but needs to be scheduled and planned for. It's better to have someone you pair with so there's a specific plan for what you want to do. At the end, everyone should present.

Proposal to once a month have a few days set aside for unstructured Angular work (e.g. we did this last week).

We'll have our hack days that thursday and friday, with presentations on the Friday.

Feb 16th, if you want to take 2 days as "hack days" you must 1) present your plan and 2) have someone interested enough to pair with you

Ongoing, let Vojta know if you want to join and didn't see last week's email.

Last week, a few people met and read some papers related to Angular, then got together to discuss. [http://shaffner.us/cs/papers/tarpit.pdf]

We have new GDEs! Dan Wahlin, John Papa, Wilson Mendes. Igor would like members of the team to sign up as mentors for them.

New York trip report from Igor. In December, a group of Angular folks went out to NYC to meet with internal and external users and speak at the meetup.

By EOW, Igor would like to have talks nailed down [link to spreadsheet] and PRs sent to their repository for the talks we're giving. Look for an email from Igor on that.

Had a kickoff today for the 1.4 cycle and the first of the beta releases should come out on Monday.

End of last year we did a big triage and fixed some issues, merged and pushed them.

Design for Forms is still under discussion. Feels like we are ready to start implementation work, but nothing gated on this this week.

Zones is in and working. You can see this in the example app. Misko to review.

Need to add benchmarks for polymer to benchpress. Igor needs to follow up on this. [Igor will own polymer in benchpress]

Naomi will check in with Yegor about porting the scroll table benchmark from angulardart, using benchpress2.

No breaking changes planned, but some style changes may have unanticipated consequences for users. Still in pre-release.

Internal users are still on 0.6.1 since we held off on a sync over the holidays. We'll be running a sync mid-week.

Julie to follow up with Marcy on the accessibility automation piece and cc Igor.

Investigating using Jasmine2 with Protractor as a framework option for people who want to use it.

Q1 Planning: Misko, Naomi, Igor working on the plan for what we'll attack. More on this shortly.

December 22 -- NO MEETING DEC 22 or 29th -- Happy Holidays :)

December 15

Agenda:

Victor will share the design doc for Forms in Angular 2 for comparison with 1.4.

Victor is looking at speed improvements in change detection this week and exploring ways of improving debugging.

Meeting tomorrow with Martin Staffa to go over improvements for Forms and potential breaking changes in 1.4. Victor will join.

Docs on publang are broken. Seems to be due to infrastructure differences between AngularDart docs and Dart docs. [Chirayu]

Two big areas of pain for users are CSS Shims and Transformers. We'll be making both of these much better in Angular 2; in the interim we've proposed some workarounds for users' specific needs and updated docs (

We did a round of triage last week and have decided on issues/PRs that will be in the next AngularDart release in the coming weeks.

We're aiming to release 0.7 RC1 on Dec 16 with the main Theme API changes and refactored tabs. This will be it for breaking changes in 2014 from Angular Material.

Goal is to have v1 of this working in angular 1.4

Meeting this Friday to figure out what to attack first and who will do what

at a high level. Still need to be split into more granular items.

December 8

Agenda:

Igor working on a doc around guidelines for communication so we get clear messages out there

There's confusion around what we're actually doing.

Will set up a mentorship program attaching core Angular team members to them to enable them with inside scoop to make them even more expert

Talked with JS style guide arbiters. Positive feedback from most teams. There are many issues to work through. Generally in agreement that we should merge with TypeScript syntax with our added features.

Igor: We should tell folks to only use https so SPDY can work

Revisiting the 'PRs Please' label to make it more useful

i18n: Pluralization and gender support will go into core template syntax for Angular 2. Will look into how to express in AngularJS 1.x (should hit in AngularJS 1.4). Meeting with bidi experts later this week.

Completed tree benchmark with early results. Already better on runtime, gc time, and retained memory than 1.x. Significantly better on memory. Will look at details and start optimizing next.

Victor Savkin: Fixed bugs in Angular 2 change detection. Can now do ng-repeat! Started support for zones in Angular 2. Should be done this week.

Misko: Spent time with Zach from Famo.us to see how could work well with Angular 2. Started documentation for Angular 2!

Victor B: Optimized change detection for Angular 2 on Firefox. There was slower on firefox vs Chrome. Now faster on FF.

that uses the new router. Looking into

Igor: Discussed service worker thoughts with Addy Osmani. Could app run in a service worker? Would need vDOM or have some hacks to make it work. Can't rely on as browser could kill it at any time...there are some hacks here.

Do we need zones for this milestone. [We think not, can wait for Milestone 3.]

Tree should be able to finish by end of the week, with some work on pre-requisites for Big Table.

AngularDart is still frozen this week. Naomi is going to run an issue triage this week to decide what we should make our top priority for AngularDart 1.x by end of year. Will pull in Rado and Chirayu and Misko to help on triage.

We need to sit down and think through what should be in draft 0 of the Angular2 docs, and get these docs written by end of year. Pete is working on the dgeni infrastructure piece. Misko and Naomi to define this.

Ongoing stability issues with the CI tests in the last few weeks due to saucelabs flakiness.

Server-side prerendering support in Angular. Should we revisit this? Igor is thinking about it and would like input from the team. Igor, Misko, Martin, and Tobias to talk more about pros and cons.

In the process of getting another 1.x release out. DNS DDOS issues are slowing that down.

Fixit event in SF was awesome. Lots of productive work on issues. Would be good to pre-screen issues next time to maximize efficiency. Should do this again.

Igor, Tobias, Vojta are going to NYC in 2 weeks. Will be speaking at the AngularJS-NYC meetup and syncing up with folks in NYC.

Jeff: Working on the Karma benchpress plugin for AngularJS 1.x. Blocked on an issue with Chrome launcher, working with Vojta. Next step is to integrate with Angular2, and to think through how to use with mobile. Also working on prototyping for difficult use cases with Ben.

Chirayu: i18n for AngularJS 1.x. Meetings this week with internal and external stakeholders. Updating the spec doc this week with some new information on decisions re pluralization and gender i18n. Starting on prototyping this week.

Rado: ViewPort for angular 2 is in. Some bug fixes, narrowing in on ng-repeat and ng-if support.

Martin: Joining the team in Mountain View. Getting up to speed on everything.

Vojta: AtScript and related discussions and implementation. Working on an example project to show typical workflow. Will loop Martin in on IDE discussion piece.

Brian: Back from vacation, porting the phonecat tutorial to use the new router for 1.x.

Misko: Docs for Angular 2 and thinking through what we need in the developer guide. Igor says, please include a glossary this time for consistency :)

). Will set up Djeni for Angular 2 next week. Hoping we can hook into AST from Traceur and not have to scrape comments. Pete and Rado will collaborate on a design doc.

Pete: Doing a release on AngularJS 1.3.4 in the next hour. Met with folks about redoing the angularjs.org site atop Material Design. Discussing what will go into AngularJS 1.4 (

Vojta: Working on AtScript in Google. Describing development workflow and properties we want out of it from the developer experience. Wrote basic version of transformer for Traceur that creates goog.module so we can use with jscompiler.

Misko: Spending lots of time discussing Issue 133 with community. I think we’re there on template syntax. Templates must be marked explicitly -- solves issues around variable hoisting. Much simpler for everyone. Thinking about what we need in terms of infrastructure for Angular 2 concepts docs. We want to deliver examples in your language of choice (ES5, ES6, TypeScript, AtScript, Dart, etc.) but we don’t like the idea of maintaining examples in that many languages. Could it be done with a special-purpose transpiler? More thinking to be done.

Rado: Got HelloWorld done for Angular2! Has injection, component, decorator to show off the basics. Implement basic version of ViewPort and working on design explanation to support template-style directives.

Victor Savkin: Change detectiong enabling/disabling record ranges so you can disable watching for portions of your app. Can also implement throttling (like once/minute) via this. Working with Tobias on benchmark around view instantiation.

. Updated tab navigation to use new spec. Changed animation curves to match the material spec better. Going through some bug fixes. Should push to master later today.

Jeff: Experimenting on moving our infrastructure to Docker on Google Cloud. Plans to finish Benchpress plugin for Karma.

. Working on supporting pluralization and gender. Working on file format / transport that we can use across many use cases. Will review with team after Thanksgiving week.

Julie: Integrating node.js with Google cloud infrastructure (protos, etc.). Met w/ Marcy on how we could automatically audit apps for accessibility in Protractor. Thinking about integrating ngHint with Protractor as well.

Matias: At GDE summit today/tomorrow. Some time for team discussions on Wednesday and Friday. Will be presenting/discussing animations work in v2 on Friday morning.

Pete: Last Friday's release is going out Monday (today). Working with Jeff on it. Planning now for a 1.4 release next year. Community interest in a docs rewrite for the Angular docs in Material Design style. Jeff will work with Pete on figuring needs for doc server for 2.0. (We should meet after thanksgiving and brainstorm)

Julie: Working on internal Google use of node.js. Working on enabling stubby calls and protocol buffers. Looking for info from other internal users on what they're interested in.

Naomi: program management. Material Design components summit last week. Version 0.6 is landing this week. Following up on security bounties. Posting the TypeScript talk.

Misko: AtScript for internal users, working with Igor on Templating syntax, thinking through web workers. Design Review after Thanksgiving would be ideal. (Naomi to set up.)

Igor: Templating syntax; close to a proposal to resolve issue 133. Will be updating the issue shortly with latest thoughts. Meetup tomorrow, and GDE summit is happening at Google, as well as the ngFixit in SF. Supporting the team.

Rado: Bootstrapping PR is out for review. Last step on Hello World is a PR from vicb on child watch groups. Next up: view port, view factory, and animations and things that view might need to be aware of. Last week, pushed vicb's tutorials for Dart tutorials and doc.

Brian: Focusing on the new router for 1.3. Improving docs around examples and porting the phonecat app to use the new router so people can look at it and comment. Working on the API around programmatic generation of URLs. Also contributing to animations with Matias.

Vojta: Started work on implementing generics in AtScript. Looked into TypeScript extensibility architecture in more detail after Anders' talk. Has been working with Michael on updating internal node.js in Google.

Chirayu: Design Doc ready for i18n. (Action: send to the team, put it in the docs folder). Design Review for Wednesday this week. Goal is to have the work broken into subtasks by end of the week and start soliciting contributions. (Naomi to schedule the review.)

Victor: Last week, merged in most of change detection for A2. Some missing pieces (plug in object.observe) landing this week, need VicB. Victor is also looking at one of the last PRs for Hello World, submitted by vicb.

People out of office this week

Thanksgiving week, who is here? Misko and Brian on Monday only, Jeff, Vojta, Victor, Rado in the office.

Demos

Naomi: In NYC working on unifying Google internal and external UI components work and planning for the next year in the Material Design project. Coordinating how Chrome V8 and Closure jscompiler will support AtScript. Meeting with these teams and TypeScript folks later this week.

Caitlin: Working on some of the hard bugs on 1.x. Struggling with some of the issues that we can't fix until Angular 2 -- will document and open for workarounds. Close to getting template literals working in V8.

Chirayu: Created a design doc for i18n work on 1.3. Compiled many issues from Google teams, will reach out beyond Google next week. Will write an idealized API that we could implement in Angular 2 and work towards an implementation on 1.3.

Igor: Helping to kick off i18n collaboration with several folks -- connecting Chirayu with all known interested parties. Participating in command-line working group to help guide where possible. Helping ng-conf folks select talks. Writing backgrounder docs on AtScript.

Jeff: Getting a Benchpress CI server setup for Angular 1.3 continuous benchmarking. Will move to Angular 2 when finished. Working on instrumenting Angular 2 with AngularHint to focus on performance specifically.

Victor Savkin: Merged Angular 2 parser into master. Now working on change detection. Looked a bit at forms, and want to have a prototype by end of this week.

Rado: Did design review for Angular 2 bootstrapping. Now working on implementing. Fixed some Traceur issues in the process. Talked to folks from AdWords about needs for multiple apps in one conjoined application. They seem satisfied. Captured in the design doc.

Vojta: Focused on AtScript transpiler progress. There is now --atscript in Traceur that enables all of our special features at once. Now finishing reexporting -- when you import and then export the same thing. Supporting folks on the AtScript playground when they have questions.

Misko: Evangelizing AtScript. Need to put the vision into a doc so we can scale and not have to be there in person every time. Our unique proposition is metadata annotations. Not everyone gets this at the beginning so we need to spend more time defining the value here. Doc forthcoming.

Tobias: Refactored the compiler - several pieces work together in the pipeline. Plan to land it in master today.

Lukas: Reviewing patches from Pete & Caitliln, triaging issues on 1.3. Need commit access!