Angular Biweekly Meeting Notes (http://g.co/ng/weekly-notes)

We started sharing the public meeting notes when the team was just a few people. Since then, the Angular team has grown, and we started using the team-wide team meeting primarily for logistical purposes - events and team-wide announcements.

Most of the relevant details about the Angular platform (framework, tooling, and components) are now part of the meetings of the individual subteams. The best resource that contains aggregated data with additional context about the team's work is available in the public roadmap, which we update before each major release.

If there's other information you're interested in and unavailable in public forums, reach out to devrel@angular.io. We'd love to connect and see how to make the information available.

September 20, 2022

• New Design docs, RFCs or NG-Elephant updates

• Doug Parker - partnerships
• Emma Twersky

• Any v15(ish) RFCs please reach out to

• Joey Perrott

• Presubmit Status Service
• Merge Authentication Service

• [Jeremy] Tech Writing
• [Andrew] Harness test migration

September 6, 2022

• ng-conf debrief!

August 9, 2022

• New Design docs, RFCs

• Doug Parker - Angular Community Partnerships
• Andrew Kushnir Pawel Kozlowski - NgOptimizedImage directive rollout plan
• Alan Agius - Angular Universal Projects

• [Minko] ng-conf

• Mark to host ngConf Family Feud! (Come and support or risk breaking his heart)

• [Joey] GitHub Write permissions changes and tooling
• [Madleina] Angular research discussion

July 19, 2022

• New Design docs, RFCs

• Jeremy Elbourn - Angular Tech Debt Summary
• Doug Parker - Angular Tooling v15 Strategy
• Doug Parker - Improve package manager support in CLI

• Welcome New people

• [Madleina] Welcome Simona

• [Minko] ng-conf & participation
• [Minko] Join the tech talk
• [Madleina] Large meeting VC etiquette
• [Alex] Debugging dependency injection

June 14, 2022

• Fix-it:

• Minimize caretaking
• Reduce the number of meetings

• Actionable issues
• DevRel updates from I/O and v14 release

May 17, 2022

• Angular v14 release photo
• Release scope and updates

May 3, 2022

• New Design docs, RFCs or NG-Elephant updates

• [Doug] Tooling project brainstorm
• [Doug] Search engine optimization
• [Doug] ng generate schematic
• [Doug] Angular Library Localization

• [Minko] Welcome Bob
• [Madleina] Welcome Alan
• [Doug] v14 release

• Feature freeze is tomorrow (May 4th).
• Add anything that needs to be done to the appropriate v14 milestone.

• https://github.com/angular/angular/milestone/107
• https://github.com/angular/angular-cli/milestone/28
• https://github.com/angular/components/milestone/30

• Escalate to the appropriate lead if anything is at risk.
• All caretakers have been added to #releasing to communicate the process and keep everyone in the loop.

• [Paul] Renaming of main branch
• [Joey] Review changes to ensure no edits after approval
• [Joey] Caretaking team update
• [Miles] CDK components

April 19, 2022

• [Joey] Feature freeze for v14 in two weeks (May 4th).
• Round Robin Sub-Team Updates

• DevRel

• NG-DE
• Speaker tracker

• [Alex/Dylan] Typed Forms landing
• [Minko] I/O
• [Minko] ngConf
• [Minko] Docs refactoring demo

March 8, 2022

• New Design docs, RFCs or NG-Elephant updates

• [Doug] User-authored custom diagnostics
• [Doug] CLI dependency checklist
• [Joey/Paul] Automating publishing of material.angular.io
• [Joey] Defining issue/PR lifecycle
• [Joey] Angular size tracking

• [Doug] v14 in 3 months

• Angular v14 progress tracking
• Documentation updates
• DevRel tracking

• [Minko] Micro-frontend updates
• [Emma] I/O updates
• [Mark] Content Casting Call
• [Kristiyan] Host elements discussion

February 8, 2022

• [Andrew] Shared Drive folder & documentation updates
• [Madleina] Remote first
• [Christina] New prioritization process
• [Joey] Security updates
• [Emma] Angular 20% opportunity for Devlibrary
• [Madleina] Black history month

January 25, 2022

• [Doug] v13.2 going out tomorrow.
• Welcome Charles!
• [Alan] Improvements in ng-packagr
• [Doug] Update CLI to RxJS v7
• [Minko/Manish] Survey results

January 11, 2022

• [Joey] - 13.2.0-rc.0 is next Wednesday (Jan 19th, 2022)
• [Doug] v14 deprecations and breaking changes - please add to the tracker.

• [Reminder] US Google Holiday on Monday, January 17, 2022 and US Googlers will be OOO, Kristiyan will be around if you need presubmits.

• [Joey] Update on Caretaking team progress

December 14, 2021

• [Joey] Releases and caretaking for the rest of the year
• [Doug/Joey] As you probably guessed, we're not directly affected by log4j
• [Minko/Jeremy/Joey] AngularJS EOL update
• [Alex] Minor releases and RCs

• Consensus: keep doing RC for minor releases, no separate feature freeze

• [Christina] Reminders - Google Reset Day this Friday, Dec 17, 2021, and this will be the last team meeting for the year.  Happy Holidays everyone! :)

November 30, 2021

• [Jessica] Angular logo pics
• [Joey] 13.1 RC
• [Doug] Add items to the v14 release scope
• [Madleina] Holiday season
• [Alex] New project proposal template
• [Doug] Ivy retrospective

November 17, 2021

• [Madleina] EnterpriseNG Tickets (12/2-3)
• [Joey] DevInfra hackathon
• [Madleina] v13 retrospective
• [Igor] Ivy retrospective
• Proposals & design docs

• [Dylan & Alex] Typed Forms
• [Miles] Rolling out MDC components to npm
• [Joey] Release Tooling Checks

• Welcome Lei Li!

November 2, 2021

• [Madleina] US Thanksgiving is coming up
• [Minko] EnterpriseNG join the event!
• New Design docs, RFCs or project updates

• [Doug] Officially support Angular builder development

• [Mark] V13 live stream on Friday, here's how you can help!
• [Alex] v13 recap

• v13.1/v13.2 dates set soonish

• [Jeremy] Material components plans
• [Emma] v13 release photo op

October 19, 2021

• [Madleina] Intro Christina
• [Emma]

• RC specific testing asks
• Documentation that introduces new pages or significant changes please also flag Emma about those changes
• [Mark] Deadline to submit feedback for release blog is TOMORROW

• [Joey] CLABot change/update
• New Design docs, RFCs or project updates

• [Charles] File replacements alternative.
• [Alex/Jess/Andrew K] Towards Optional RxJS in @angular/core
• [Joost] NgSwitch type checking proposal

• [Dave/Alex] Updated Project Proposal Template
• [Jeremy] Tackling large and small projects and individual project load

• Mark: could try alternating between released packed with small improvements and releases with major shifts
• Andrew K: FR triage process is a good place to identify low-effort features. Could try to foster more community contribution for these types of tasks.
• Andrew K: more visibly track the impact:effort ratio
• Doug: want to have more people involved in prioritization
• Alex R: it's good for some folks to have two projects going at a time, one large-scale and small-scale

• Of course this varies from person to person based on work style

October 5, 2021

• v13 Features demos

• [Paul/Igor] APF v13 changes
• [Andrew K] Factory-based APIs cleanup
• [Doug] Dropping IE polyfills migration

• [Minko] DevRel Update
• [Madleina] OKRs !

September 21, 2021

• [Joey] Hacktoberfest 2021
• [Madleina] Design doc roles & expectations
• [Zach] Quick Kythe demo
• [Igor] v13 feature freeze coming up
• [Minko] DevTool Update
• [Joey] Welcome Caretaking Team
• [Madleina] Welcome Deej
• [Madleina] Welcome Sarah

September 7, 2021

• [Doug/AndrewK] Ivy in g3 default flag flip
• [Alex] Tech Talk: Rust WASM compiler by Alex

August 24, 2021

• [Dave] Welcome new writers!
• [Joey] Dev Infra Fix it Week
• New Design docs, RFCs or project updates

• [Pawel] Standalone components / design review invitation. You can also play with the API in stackblitz!
• [Andrew K] Proposal: factory-less APIs cleanup for v13 and Proposal: explore more ergonomic APIs to replace *Ref ones
• [Igor] RFC: JIT compilation use-cases

• Imperative View & Template Composition APIs
• Out-of-band type-checking for TypeScript and Template compilation
• Transition Angular from the whole-program compilation to localized compilation

• [Doug/Alan] RFC: Persistent build cache by default

• [Jeremy & Dave] Documentation-first development
• [Daniel] Final extended template checks demo.

July 27, 2021

• [Madleina] OOO availability notices
• [Jeremy] Reminder about 12.2.0 coming up
• [Jeremy] Reminder (pause to celebrate?) that we can start removing code for IE11 support post 12.2.0
• [Jeremy] Check-in on the v13 release plan (and making sure we have everything captured)
• [Minko] Reminder that folks could volunteer for:

• Writing a blog post for blog.angular.io
• Giving a talk on a community meetup
• Recording a video for our YouTube channel (we need to be back in the office so GDS can help with equipment)

• [Alex] Celebrating wins

• [Daniel] Extended checks prototype
• [Pete/Joost/George] ES2017 transform prototype

June 29, 2021

• [Minko] Welcome Alex (Aleksander Bodurri)!
• [Doug] Welcome Daniel!
• [Madleina] July 4th heads up

• Off July 5 and 6
• meetings will be canceled for those two days
• We will also skip next week’s releases

• [Alex] Team wins & mini demos

• Joost on ES2017 transforms
• Daniel on his intern starter project

• [Jeremy] Be on the lookout for v13 community contribution opportunities
• [Joey] CI outage update & plans forward

May 5, 2021

• [Jen] Welcome Dylan + Amy!
• [Dave] Documentation updates
• [Jeremy] v12 release

• PRs targeting next and patch need to be merged by Friday, including documentation

• [Minko] I/O updates

• happening on May 18, Angular will be a part of the web track

April 4, 2021

• [Jeremy] v12 update

• Feature freeze: April 14th

• [Minko] ng-conf

• April 22nd and 23rd
• Talent Show!!

• Please complete this form to participate

• [Keen] Formalize our policy on compatibility between app and library

• Enforcement is done via peer dep today, but failure to comply only generates warning prior to npm v7
• AI: Document our policy on angular.io
• Discussion: in v12, should we compile libraries in partial format by default?

• AI: Will discuss in follow up meeting

March 23, 2021

• [Cindy] Reminder: Friday 3/26 is a Googler day off (“Google Recharge Day”)
• [Igor] Library authors in v12

• current (problematic) v12 plan:

• CLI is about to remove VE support for apps and libraries
• FW is about to announce VE deprecation
• all @angular/* packages to ship in VE
• 3rd party library authors not interested in Ivy/linker library format because they don't want to be the first to drop VE support

• options:

• #1 do nothing
• #2 drop only VE support for apps (keep it for libraries)
• #3 drop VE support from FW (and publish all @angular/* packages in the Ivy format)

• resolution

• option #2

• VE deprecated as of v12
• CLI no longer supports building apps with VE in v12
• CLI still supports building libraries with VE in v12
• in v13 VE is no longer supported for libraries

• [Joey] Angular Framework and Tooling together in a repo

• Bazel integration
• Takes an hour for end-to-end testing
• Tooling prefers to test in CI vs published version
• Might introduce a lot of churn (git history -- can this be retained?)
• Google3 sync process is different for both framework and tooling
• Would this lead to merging of components repo as well?

• Doesn’t automatically mean we will/will not merge components

• Web sites would need to be merged

• Docs publishing would be easier

• Would this create a burden on those who merge PRs?

• More on fw vs tooling

• Conflates the issue count
• Timing?

• Separate project proposal or fast track?
• Ideal opportunity would be to perform the merge after a major release

• Concerns about potential DevEx experience degradation
• Next steps:

• Joey to create a project proposal (following additional discussion)

• [Minko] DevTools access
• Announcement: Angular v12 feature freeze is in 3 weeks (April 14th)

March 9, 2021

• [Jen] Team check-in
• [Jeremy] Angular v12 update: on track for May 12, 2021

• IE11 deprecation + RFC
• Add support for Node v14 (active LTS started Oct 2020) in Angular v12
• Upgrade Node to v14 in FW and CLI,
• Run nightly CI for Node v12

• [Minko] ng-conf participation call for participation

February 2, 2021

• [Minko] ng-conf Angular team interviews: reach out to Minko if you’re interested in doing a pre-recorded 5-min interview. looking for 8-10 folks to participate!
• Expanding the team

December 12, 2020

• [Minko] Angular developer satisfaction surveys
• [Joey] Caretaker

• #caretaker Slack Channel
• Weekly Caretaker Debrief
• Proposal

• [Cindy] Announcements:

• No meetings Dec 18 - Jan 4 (team and retrospective meetings have been canceled)
• Caretaking rotations will end on Thursday, December 17th (and resume on January 5th)

• Merging will still continue for FW and CLI
• No merging for Components

December 1, 2020

• [Minko] NGPoland, JSPoland, EnterpriseNG, and NG+

• 5k+ folks viewed 11 talks from the team

• [Minko] ng-conf in 2021
• [Igor] Current release dates targets

• Jan 13, 2021: v11.1
• Feb 10, 2021: v11.2
• May 12, 2021: v12

November 17, 2020

• [Dave] Welcome Teri!
• [Minko/Emma/Mark] v11 release community feedback
• [Jen] Team check-in

October 20, 2020

• Welcome Jessica & Zach!
• [Jen] Team check-in (spreadsheet)
• [Alex/Andrew] Ivy Language Service demo
• [Jen] Angular release schedule/planning update

• v11 = Nov 11
• v11.1 = Jan 13
• v11.2 = Feb 10 (tentative)
• Release calendar

October 6, 2020

• [Jen] Team check-in every 4 weeks
• [Jen] New teammates!
• [Joey] Hacktoberfest
• [Emma] Twitter dashboard
• [Minko] Conference talks and blog posts ✨
• [Cindy] v11 update

• Currently underway: TLs are finalizing scope
• October 14 - feature freeze (next week!)
• October 21: First RC
• October 28: Second RC
• Nov 4: Final RC
• Nov 11: Release
• Reminder: Please don’t forget about documentation

September 22, 2020

• [Jen] Team check-in (spreadsheet)
• [Alan] Updates from the RFC for removing render blocking resources (https://github.com/angular/angular-cli/issues/18730)
• [Minko] NG event announcements

• JavaScript LA
• Dutch Angular Meetup
• Firebase Summit
• EnterpriseNG
• ngChina
• ngRome
• NGPoland

September 8, 2020

• [Jules] Meeting kickoff
• [Emma] Community feedback, more community touchpoints
• [Mark] Understanding challenges with the beginner journey for Angular

• ::ng-deep
• Which path to take?
• Examples
• Change detection
• RxJS

• [Minko] Strict mode user feedback
• [Joey] `master` branches are now targeting 11, allowing breaking changes

August 8, 2020

• [Minko] Customer updates
• [Minko] Roadmap feedback
• [Alex] RFC community response
• [Alan] Eliminate Render Blocking Requests RFC proposal
• [Keen] Removal of solution-style tsconfig in v10.1
• August 18th: Intern Project Showcase!

July 28, 2020

• [Stephen] Working on pushing forward more community involvement, feedback
• [Jules] Team check-in
• [Jeremy / Keen] Operation Byelog update

• Alternating 2 week cycles
• Framework has ~450 untriaged GitHub Issues
• Components has ~40 untriaged issues
• Tooling has all issues triaged
• We've been able to categorize issues and fix multiples at a time
• Some issues are help wanted
• PRs Next

• [Alex R] Going to be collecting community feedback on our Ivy for Libraries plans soon

June 16, 2020

1. [Jen] Team check-in
2. [Keen / Misko] v10

1. There was a breaking change in a patch to TypeScript 3.9
2. If you want a change to land in the master branch, target master only, or split your PR.

3. [Jen] Code reviews should be hard interrupts

1. Speed is critical
2. Escalate quickly

4. [Minko] Looking for ways to support the black community
5. [Minko] Angular/AngularJS split in the Stack Overflow Survey

June 3, 2020

1. [Jen] Team check-in

1. Jeremy will be helping with Framework

2. [Jeremy / Stephen] 3 Summer Interns Starting
3. [Pawel] Fixit update

1. Made progress, great experience for the team
2. Touched / reviewed around 2000 issues
3. Fixit retrospective
4. Components triage took about 10 minutes per issue, framework took more

4. [Igor] v10 rc 2 is out

May 19, 2020

• [Jen] Team check-in
• [Joey] DevInfra Update

• Working to trigger CI runs when specific labels are added
• New infrastructure tools

• Know how many other PRs conflict with a proposed change, measuring "churn" caused by a PR
• More consistent merge tooling

• [Pawel] Fixit starting next week
• [Jen] Roadmap planning

• v10 RC next

April 21, 2020

• [Jen] Team check-in
• [Jen] v10 Planning Update

March 24, 2020

• [Jen] Team check-in
• [Igor] Framework & CLI  v9.1 rc.1 is out, Components v9.2
• [Joey] DevInfra Update

• Started using Paul's new tool to check for circular dependencies
• Using a new private dev-infra npm package that can be shared across repositories

• [Stephen] ng-conf 2020

• 11 team speakers, everyone remote, most talks livestreamed

March 10, 2020

• [Igor] v9.1 focused on TypeScript 3.8 & parallel ngcc, then onto 10

February 24, 2020

• [Stephen] v9 still receiving more and more positive feedback
• [Joey] DevInfra Update

• Framework integrations test running via Bazel, making tests faster
• Yarn versioning (ensuring the version of Yarn) deployed across all three main repos

February 10, 2020

• [Igor] v9 Launched!
• [Stephen] v9 success metrics very good

December 2nd, 2019

• [Manu] v9 update
• [Minko] Europe trip report (ngPoland, jsPoland, etc)
• [Vikram] Welcome Wagner - looking at ng deploy, and server side rendering

November 4, 2019

• [Igor] Welcome Doug Parker
• [Jules] Welcome Cindy Greene-Kaplan!
• [Igor] 9.0.0-rc.0 shipped! Check out update.angular.io and give it a try

• Triaging issues reported, identifying v9 candidates and blockers

• [Manu] v9 update

• Uncovered i18n issue that can sometimes break pipes & pluralization
• Following up regarding runtime errors with library authors
• Changes to v9 must be targeted to "master + patch". Changes to v8 will need merge assistance.

• [Joey] DevInfra - Giving feedback to GitHub and CircleCI about our experiences

October 7, 2019

• [Igor] v9

• Several apps now on Ivy (material.angular.io soon, next.angular.io)
• Most of size gap for medium apps closed, simple and complex apps are smaller

• [Stephen] AngularConnect 2019 was a big success, blog post coming soon
• [Alex R] Progress/NativeScript visit went well, several apps working with Ivy + NativeScript
• [Joey] CI outage last week for a few hours. Please rebase your PRs.

September 9, 2019

• [Igor] great work over the last 6 months from team, collaborators, contributors. A huge thank you to everyone!
• [Kara] Ivy Status report

• Runtime performance is on par with view engine, styling refactor merging soon
• CLI Hello world under 100kb
• Looking into compressibility of Ivy (compression characteristics are a little worse)

• [Stephen] 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.
• [Jeremy] Components update

• 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.
• Example harness: https://github.com/angular/components/blob/master/src/material-experimental/mdc-tabs/harness/tab-group-harness.ts
• Several MDC-based components in @angular/material-experimental
• Introducing @angular/youtube-player
• Working on @angular/google-maps

• [Vikram] Tooling

• 8.3 builds are faster because we downlevel from es2015 build, instead of doing two builds
• 8.3 New `ng new` experience by Stefanie
• 8.3 Introduced ng deploy command
• 9.0 focused on preparing for Ivy

• [Joey] DevInfra

• Locking issues that are closed and inactive, sorry for the emails!
• 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
• Charles built lockbot

• [Stephen] Angular Connect is next week! 10 folks from the Google team presenting

August 1, 2019

• [Igor] Welcome back Jules!
• [Misko] Welcome Andrew Scott!
• [Kara] Ivy Status report
• [Joey] CI & DevOps Update

• Looking into TypeScript/Bazel speed improvement opportunities
• RBE: Linux Works, Mac builds but doesn't yet test
• Investigating Test Driven Development experience, eliminating duplicate file change checks

• [Igor] Starting working towards 9, cutting 9.0.0-next.x releases

• Plan (subject to change):

• Ivy default for Applications (allow opt-out)
• Libraries should still ship View Engine Code to npm
• Framework will ship View Engine Code to npm
• ngcc will translate everything for applications
• We will ngcc es2015 libraries, and then we will downlevel (instead of running ngcc on es5 libraries)
• Planning to remove opt-out in following version

• Tracking Library compatibility here: https://github.com/mgechev/ngcc-validation

July 15, 2019

• [Igor] We're hiring!
• [Stephen] DevRel Update

• Refer great new GDEs, especially historically underrepresented groups
• Pushing folks to try Ivy and file feedback & reproductions

• [Joey] Introducing our Developer Infrastructure focus

• Migrating tools, framework, and material to Bazel for CI and local development
• Improving Windows developer experience
• Measure build & test performance

July 1, 2019

• [Kara] Welcome Alyssa!
• [Kara] Ivy Status report
• [Stephen] DevRel Update

• Prototyping with Angular - see the cool Firebase & Google Sheets Integration
• Bazel opt-in Preview

• [Minko] CLI Survey Results

June 17th, 2019

• [Igor] Version 8 highlights

1. Improve Build (differential loading, etc)
2. Improved Upgrade Experience ($route/$location/etc)
3. Improvements to CLI (Builders, Workspaces, etc)
4. Docs updates (deprecations, new getting started)
5. ng update success

• [Kara] Ivy Status report, opt-in preview is out, making progress
• Trip Reports

1. [Rob] AngularUp
2. [Minko] Various Trip Reports
3. [Stephen] AngularMix

May 20th, 2019

• [Manu] Cleaning up version 8 milestone
• [Miles] Exploring creating new harnesses to make testing Angular Material and CDK easier

April 8th, 2019

• [Stephen] New Getting Started launching soon
• Introduce new Collaborators (Jason B, Deborah K)

March 25th, 2019

• Introduced new Collaborators (Adam P, Jia Li, Sam J)
• [Manu] Status update
• [Stephen] ~32,000 developer survey results, developers cared most about runtime performance. Happiness and ease of updates both improved. Blog post under development
• [Misko] hackmd.io is an interesting tool for editing and collaborating in markdown
• [Andrew Seguin] Demo of concept: dashboard & query & notification tool for GitHub

February 25th, 2019

• [Igor] We're trying to expand our support for top Angular contributors (called Collaborators) with mentorship
• [Miles] New best practices for breaking / deprecating APIs in Angular
• [Misko] Giving constructive feedback presentation
• [Misko] How CPUs work presentation
• [Manu] Status update

• TypeScript 3.3.333 helps us

February 11, 2019

• [Stephen] Version 8 plan published
• [Igor] Great community feedback about ngUpgrade
• [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
• [AlexE] Don't copy 3rd party code into the angular/angular repository without appropriate licensing and documentation. README in the third party directory coming soon
• [Igor] Great thinking about API and language design in this video: https://www.youtube.com/watch?v=_ahvzDzKdB0
• [Misko] Kara is now tech lead (TL) for Framework subteam! This change enables Miško to focus on deep technical issues and the future of Angular.

February 4, 2019

• Last week's releases went smoothly. (7.2.3, 8.0.0-beta.2, CLI 7.3.0, 7.2.4, Material 7.3)
• Caretaker Escalation Process

• Need to update process to surface productivity issues
• Caretaker needs to own CI instability

• Considering changes to release & branch naming

1/28

• [Igor / Manu] Version 8 plan updates, current status (not accessible to non-team members, public version coming soon)
• [Igor] NYC trip updates 

• bazel
• stofe-infra / pantheon
• dbm / dcm
• firebase console
• Chrome / Workbox
• Angular Meetup

• https://www.youtube.com/watch?v=a3j5U5WVmUo
• https://www.youtube.com/watch?v=fEUgZopCK8E

• [Stephen] DevRel update
• Super quick FYI: It's Sass, not SASS (Jeremy)
• [Igor] retrospective next week
• [Igor] Office decoration proposals review and call for votes

• please +1 on title or voice concerns by tomorrow COB

• [Jeremy/Vivian] Contributor shirt

1/14

• [Igor] The doc about Angular (team-only doc for now, sorry!) and next steps
• [Igor] v8 plans 
• [Igor] better @ open-source plans
• [Joey] CircleCI Github Checks vs Github Status, permissions
• [Joey] Splittin Angular Material BUILD rules, deeper imports
• [Igor] Slack notification life-hack
• [Brad] Trip report from ngAtlanta

1/07

• [Kara] Review caretaker process / logging ?

• log.angular.io

• [Alex] Ivy/Framework productivity updates

• Tooling team focused on productivity problems
• Made strictness checks faster
• Jasmine tests 25% faster
• Prevented new deps on (slow) ng_packages
• Upgraded to Bazel 0.21 with fix for incremental rebuilds
• Jasmine node test stack traces now CLICKABLE in editors
• Next:

• Stack traces from Karma tests
• Switching dev mode to ES2015 so you don't see down-leveled code
• Adding Windows CI so we know of breakages on buildkite (not CircleCI)
• Compile time improvements for tslib - moving ngtsc into library rule to remove angular specific compiler rules
• Splitting big packages for more incremental compilation

• [Igor] CI infra updates

• Pullapprove => CodeOwners migration landed PR#27690
• CircleCI Perf plan enabled since early Dec - no more build queues
  Travis => CircleCI move PR about to land PR#27937 (30-40min => 10-11min)

• [Vivian] Component overview
• [Miles] Collaboration with MDC (team-only doc for now, sorry!)
• [Igor]  v8 release schedule, should we do 7.3 in Feb or skip?
• [Igor] reminder: Various ad-hoc documents and documents presented in the team meeting are not accessible to team@angular.io - this prevents team members from accessing them (e.g. tech writers, tooling team, etc)
• [Igor] Office decoration proposals review and call for proposals (team-only doc, sorry!)
• [Brad] Team offsite

12/17

• Branch Management - Cherry-pickability and Auto Cherry-picking (Joey?)
• v7 Retrospective next actions (Manu)

• Infrastructure stability improvement: PullApprove => CODEOWNERS migration propropsal https://github.com/angular/angular/pull/27690

• 2019 Conference Plans (Stephen)
• Best Practices sharing (Igor)
• Setting up DNS records  Documentations (Joey)
• DevRel Updates (Brad/Stephen/Rob/Minko)

• Ivy emit source code size https://github.com/mgechev/ngtsc-benchmark

12/10

• v7 Retrospective

• Put your feedback into the survey ahead of time!
• Calendar invitation has the link to the survey, sent to team email alias

• Ivy update

• Primarily working on getting all framework tests running w/ Ivy
• This initial testing step down to diagnosing the last few dozen issues
• Also working on getting Angular Material dev app working. A handful of the simpler components are functional.

• rules_typescript regression

• Identified a regression over the weekend in Bazel's rules_typescript.
• Compilations were not type-checked
• Does not apply to code compiled with the ng_module rule, only ts_library
• Caused by code being omitted inadvertently when synced from Google to GitHub

• Writing good commit messages (Alex R)

• Use a descriptive, accurate title
• Commit messages can be more than one line!
• If changing a behavior, describe both the old and the new behaviors
• Reference bugs and/or task ID from task trackers in the commit body, not the subject.
• Keep commits focused on a single purpose
• Small commits are easier to revert
• Remember that the PR description is not the part of the commit history. Use the PR box for things related to review rather than the change itself.

• FBB team fun event
• Other topics ?

12/3

• Passed 1.5M monthly actives on aio - More than 50% YoY growth!

• Tweet with thank-a-thon starting today

• Site move - pack your boxes by Friday!
• Bowling this friday!
• Ivy plan update
• CircleCI / Engineering productivity update

• Remote caching and remote builds coming soon

11/19

• Ivy plan update

• Focused on getting existing tests passing
• Still some duplication and missing knowledge on efforts

• Handling stress
• Circle CI

• Igor writing postmortem on outage
• Want to improve our responses in the future

11/12

• AngularConnect Recap
• Ivy Update
• On to v8!
• Overview of merge ideas (jeremy)
• Welcome Minko

11/5

• Ivy Styling (Matias)

10/29

• Ivy Compiler (AlexR)
• Office move update

• MTV
• SFO
• MUC

• FBB All Hands tomorrow
• Ivy update

• All bits of runtime save i18n have landed
• Getting TestBed to pass -- now 75% green
• Then get Material components working
• Then sync to google and run angular.io running
• Last bit will be getting i18n atop Ivy (just 2 PRs in review to go!)

• NativeScript 5.0 update
• Branch Management Presubmit design (Joey)

10/22

• v7 Celebration
• 7.1 targets (~1mo after 7.0)

• Tooling:

• Adding build event outputs as JSON so Angular Console can show progress

• Will use Bazel's build event protocol for this

• Schematics & architect work so you can do ng whatever with --prod
• Fixing perf & build size regressions found with a few customers

• Framework

• Routing & Forms bits on the list

• Material & CDK

• Small feature additions...nothing major

• 2019 Roadmap
• Ivy

• Enabling all tests in Ivy and have a tracking spreadsheet of all tests
• This week resolving gaps in test infrastructure
• Will be asking for more help from the rest of the team to work on integrations at Google and CLI
• Kara presented on the runtime architecture

• infrastructure updates

• Bazel

• Landed big change on Friday making Bazel execution faster both locally and remotely

• angular.io CI jobs

• Moving more stuff from Travis to Circle (blocked on GitHub outage)
• Improves CI time from 25min to 7min
• Only framework integration tests remain on Travis. Igor will reach out for help.

• Github Outage

• CI likely in bad state for rest of today

• DevRel

• Angular Connect (AlexR, Igor, Martin, …)
• Also going to ngPoland/JS Poland, ReactiveConf, Carribian Dev Conf
• V7 being well received by community

10/15

• Angular Mix update
• Ivy Focus Plan

10/8

• V7 update
• CLI in g3 demo
• AngularMix plan
• Hiring jamboree

10/1

• Welcome Andrew (Andrey)
• RC update

• bugs
• doc clean up
• GDE feedback
• targets, labeling, branching

• Conferences

• Mix
• AngularConnect

• Vacations for Q4
• Bug / PR process updates
• Ivy update
• Intern Projects

• Martin
• Jeremy
• Keen
• Stephen
• Manu / Andrew
• Hans
• Kara
• Matias
• Rob

• Angular class for Wiz
• Angular in google3 update
• FBB Social

9/17

• Proactive support for Googlers

9/10

• Future of Angular Elements (Rob)
• Angular Labs (Matias)
• DevRel Update (Stephen)
• Long term vision discussion (Brad)
• Program update (Manu)

8/27

• 2019 funding
• DevRel update

• AFIS
• JSConf
• Talked at BlackRock last week
• Presented AngularJS to Angular migration support/tooling at last week's meetup
• Ionic working on ng add support
• Angular Console by Nrwl launched - one-click install for Angular development
• 77 GDEs now!

• Program status update
• Angular Labs update

8/20

• Skipped this week.

8/13

• Angular Labs infrastructure and process (proposal shared with team members - not externally visible)
• Upgrade Support report
• Jaron chat about results on autodeps for Bazel
• Moving next week!

• Your Move Will Take Place the Morning of: Wednesday, 8/22
• Move Time: Between 5am-8am
• Please Be Packed and Powered Down By: 7pm on Tuesday, 8/21
• Boxes & Labels Will Be Delivered By End of day on Monday, 8/20
• Everyone should report to 1225 on 8/23.

7/30

• Moving update - Week 8/20 to 1225 Charleston (December 1225 Crossman)
• DevRel Update

• Rob spoke at Cloud Next with IOT team - the demo worked! :) Video is live.
• Joey worked in the Grab n' Go Loaners booth. App built in Angular! Blog post coming soon.
• Presented remotely to ngHouston about Angular for Designers
• Going to Atlanta today to talk to IBM folks
• Going to JavaScript Atlanta
• 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)
• Rob going to Angular Denver on Wednesday
• Vikram (Universal) and Igor (Panel on tooling and frameworks) presented at Node Summit

• Vikram presents from his NodeSummit preso

7/23

• Security practices (jelbourn)
• DevRel Update (Stephen)

• Rob & Hans went to TransUnion bringing them up to speed on all our best practices - much excitement around the CDK
• Collaborating with Women Techmakers here at Google
• Vikram speaking at NodeSummit and internally with Stephen at MobileWeek
• Several blog posts coming up - one on the Grab 'n Go loaner project
• Rob presenting at Google Cloud Next
• Stephen at ngHouston

• Program Update (Manu)
• Jira demo (Jason/Manu)
• SLO preview (Manu)
• Org change updates (Brad)

7/9

• V6.1 update
• V7 update
• DevRel update

• Brad went to Worker.sh in Austria and talked about Angular Universal
• Rob went to AngularUp in TelAviv. ~600 folks. Did Angular Girls session.
• Had announced AngularJS LTS. Several blog posts hitting now on this.
• Chatted with SAP on MetaUI plans.

• Q3 OKRs

• Material - Jeremy

• Vscroll
• Drag & drop
• Accessibility improvements

• Framework - Misko/Manu

• Ivy - define deliverable
• Pantheon deliverable
• V7 deliverable
• Elements on Ivy
• Tech debt fixit sprint - finish Bazel migration

• Tools - Igor/Manu

• CLI in g3
• External enterprises using cloud builds / build farms
• Angular GUI
• Serving solutions

• Typescript - Martin

• AngularJS Release Plans

• Announced that we'd go LTS July 1.
• But still we have some work done somehow… :) A few more releases around Web Component support and bug fixes.

• ABC progress and plans

• Early access

• Have bi-weekly chat with adopters
• Have a few enterprises actually using it
• Lazy loading strategy uses Rollup. Also have a Webpack version. Need to invest to get this working for the full solution.

• Rainbow

• Focusing on remote build execution (RBE)
• Working on hiring for this
• Now have saucelabs builds working similar to how we do it in g3

• Should dogfood this in the Angular build first

7/2

• DevRel update
• Angular 6.1 planning

• Framework
• Shadow DOM v1 (https://github.com/angular/angular/commit/49c5234c6817ceae02b8bacb30adae99c45a49a9)
• TypeScript 2.9 (https://www.google.com/url?q=https://github.com/angular/angular/pull/24652%23issuecomment-399888270&source=gmail&ust=1530637370825000&usg=AFQjCNE9YuVjgIIDgxjnY_6tyl9Yb18pMg)
• Router scrolling restoration service (https://github.com/angular/angular/commit/49c5234c6817ceae02b8bacb30adae99c45a49a9)
• Reactive forms docs update announcement
• CLI

• repository unification (devkit --> angular-cli)
• direct webpack configuration file build support (https://github.com/angular/devkit/pull/946)
• `ng update` support for private packages/registries (multiple PRs)
• as well as a large amount of bug fixes

• Material

No plans for next minor at this point

6/25

• Demo: Reviewing PRs
• DevRel Update
• Milestones update
• Angular in G3

6/18

• GSX Universal launch imminent
• DevRel

• AngularUp - Israel
• OsConf - Pakistan
• ngJapan - Miles & Kara
• Charter Communications this week w/ 100s of Angular developers
• Added 2 more GDEs
• FluentConf
• Angular Mountain View

• Milestones update
• State management recommendations

• Options

• Flux-basic-style

• Redux
• Ngrx / ngrx-data

• "Ergonomic" but non-serializable, non-resumable

• MobX
• NgXs

• Must be a tree, not a graph

• So you can serialize
• So you can resume vs replay

• Need to investigate boilerplate reduction options
• Want to get to the point where everything in Angular is lazy loadable

6/11

• Angular community momentum

• Internal adoption growing (600 to 700 projects in the past 2 months)
• Reached our yearly external user goal IN MAY
• ABC funded with 5 new HC

• DevRel

• Gave a talk for ACM Learning Webinar (600 attendees, audience questions here)

• Top Questions

• Why Angular (I"m coming from AngularJS/Vue/GWT)
• What should I use for state management?
• How do I get started?

• New GDE: Fabio Biondi
• Government loves Angular - many gvt CTOs leading migrations to Angular
• Alex Eagle is doing a great job with his Early Access Program & Support for companies who want to use Bazel.

• Ivy

• Queries now working!!!
• Nearly done with viewContainerRefs
• Rewriting SVG
• Inheritance for Material, etc. coming soon
• Will land build for ext world in JIT mode coming soon (or has landed?)
• Ngcc kicking off today
• Misko doing state management library research
• Have PR out for ngtsc-JIT that compiles the TODO app

6/4

• Welcome interns!

• Victoria
• Elana
• Jaron

• DevRel Update

• Rob at SharePoint north america talking about Elements for CMSs
• At AngularBoston, Angular Contributor Day, and Progress Next last week

• Kendo adding ng add and ng update support

• V7 plan updates

• Ivy

• Getting tests running (vic)
• Fixing memory pressure issue (kara)
• Query support (Pawel/Marc)
• Creating distro (alexr)
• I18n (Olivier)
• SVG namespace (ben)

• G3 Plan

• Server side rendering
• CLI
• Docs refresh

• Zoneless

• Need to eval NgRx current state
• markDirty API
• Testing replacement for fakeAsync
• User latency tracking

• CLI

• Moved tests and code inside DevKit repo
• Docs in aio
• Extensible builder format
• Workspace library
• CLI in g3
• Refactoring library design review
• Schematics: prompt support

• Elements

• Ivy
• Community bundling solution

• Material

• MDC evaluation

• Possibly make visual updates

• Vscroll
• Drag
• FlexLayout

• ABC

• Auto-maintaining build files
• Onboarding big orgs
• Finishing angular migration to Bazel

5/21

• (rob+jeremy) Angular Material, Zones, and Elements
• (miles) Demo: virtual scroll
• (manu) V7 plan

• High level plan done
• Work breakdown to be done this week

• (stephen) DevRel Update

• Presented at WeAreDevelopers

• 8 Googlers + 8 Angular Community Members
• 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
• At ProgressNext show next week

• (alexr) Ivy TODO app -- now with JIT!!!
• (igor) Seattle Visit next week

• Several of us going to work with Google Cloud team on their architecture plans
• Will also visit the TypeScript team to chat about feature requests

5/14

• Retrospective follow up
• Ivy planning
• G3 planning

5/7

• Discuss potentially automatically locking old closed github issues (josephperrott)

• Yes!
• On inactive for >1month
• With message that folks should open new issues and refer to this one if there's a regression
• Should we auto-close open old issues?

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

• Joey will file the issue

• Retrospective next steps

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

• Version 6 follow-on

• Things in g3

• Piloting Universal with a team

• Getting nodejs working in prod at Google!
• Working on benchmarks
• Will present next week with plans

• Making a plan for CLI at Google
• Helping Pantheon with architecture

• Framework

• 6.1 will have TS2.8
• Then focus on v7

• CLI

• Many things we want to do!
• Meeting today to plan ordering of desires

• Material

• Virtual scroll
• Drag & drop
• Accessibility improvements
• Many other small improvements (table, etc.)
• Switching package to use Bazel build/test

• Version 7 Planning

• Have a strategy doc that Misko will present at next team meeting
• Manu will own breakdown into a work plan to present in 2 weeks

• Dev Rel report

• Presented remotely at Angular Bolivia
• Same for Melbourn
• Adding 5 more GDEs (total now around 65)
• Have meetings with new enterprises every week with 100s of developers each

• Speaking events

• What's going on at I/O

• GDEs visiting us here
• Doing an Angular public social tonight
• Speaking on Wed at 4:30pm on What's new in Angular + Ivy (Kara + Stephen)
• Have a booth in the Web + Payments tent
• The biggest ngGirls event ever happening this week with 144 attendees

• Rob is at Microsoft Build this week
• Also talking at We Are Developers in Vienna next week (Stephen)

• Caretaking app demo
• Hoodies

4/23

• Recap of ng-conf
• Plan for v6 ship

• CLI - several open blocking issues. Hans working on plan for this.

• 22 open blocking
• Needs more in-depth triage.

• Creating update.angular.io for easy walk thru for folks upgrading
• Docs has a few issues. Most blocking things already merged and ready to go. Just nice to have stuff left.

• Many visitors this week!

• CLI team
• NativeScript
• Amadeus

• Retrospective for v6

4/2

• [manu] Things to do in v6

• Elements: needs polyfills infra - target for next RC on Wednesday
• ng_package bazel rule needs update to work with Material (and probably others)
• 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.
• CLI pushing RC today.

• [brad] New slide deck format

3/26

• Changing this meeting time

• Moving to 11am Pacific
• No standup on Mondays

• Things for v6

• CLI

• PWA and service worker are done
• Critical RxJS issue - Ben fixed, needs review and merge
• Hoping for RC this week

• RxJS

• Found issues with RxJS - Rob working toward fixes
• RxJS now in g3 with backward compatible patch, now removing patches
• Meeting on the update story to agree on public path to get to 6

• Material

• Landing 2 PRs as fixes to angular/angular
• Needs namespacing of private export symbols
• Then need new Angular RC
• ...and we may be good for RC

• Framework

• Elements in good shape. Possibly needs an update for treeshakable injectors
• Will update Angular to use APF instead of build.sh

• Docs

• On track for Elements, treeshakable, etc.
• Needs new example for treeshakable

• Angular Survey results
• Googlegeist results

3/12

• [jeremy] ng add demo
• [manu] v6 plans and updates
• [brad] speaking opportunities questions go to stephen

3/5

• [igor] update on caretaker role and responsibilities

• Health of CL and health of g3w

• [misko] review Ivy DX Questions (internal only)
• [manu] v6 plan
• [stephen] ngLarge debrief
• [jeremy] matSelect

2/26

• [brad] fun stuff going on this week

• Partnerships
• ngLarge summit
• Pantheon summit
• Angular + AMP

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

• example

• [brad] Ivy process and expanded roadmap

2/12

• V6 updates
• [Andrew] Demo Angular Elements in angular.io
• Googler-only topic

2/5

• [Chuck] Demo Hello World with Ivy
• [Igor] talk about features of V6 (why it is worth it even without Ivy)
• [Igor] talk about elements and their benefits (even without Ivy small size)
• [Igor] Pantheon: New rules of engagement
• [Misko] Ivy status update: #21706
• [Brad] Update from ngAtlanta conference

• Cool new conference - felt very Angular-ey (warm, inviting, open)
• 70% women speakers
• Overall awesome except for starting at 8am! :)
• Much excitement over our plans for Elements, Bazel, and ng update in particular

1/29

• Angular tV6 Sprint updates
• Q1 and 2018 Yearly Goals review

1/22

• Animation design review scheduled for later this week
• v6 plan review

• Framework and Infrastructure deliverables on Github in v6.0 milestone
• CLI, ABC and Material tracked in respective projects

• Sprint planning consolidation

• We are consolidating several sprints plannings into just Framework, Material and CLI
• Current sprints run as planned, consolidation takes effect at the end of the current sprint

1/15

no meeting - holiday

1/8

• Bazel update (Alex)

• Switching Angular repo to work on Bazel to improve our productivity
• Reduces # of tools we use internally vs externally (sharing build config too)
• Dogfooding the ABC project on road to helping other companies use Angular with Bazel

• Angular 2018 developer survey went live!

• Have 3K results on main survey and 1K on extended survey (this is amazing)
• Will keep running for another week

• 2018 conference plan (Stephen)

• Each person gets 1 Angular conference and 1 non-Angular conference
• Send conference desires for Q1/Q2 to Stephen by end of this week

• New status dashboards

• team.angular.io (internal only)
• status.angular.io (public)
• hq.angular.io (public)

12/18

• Bertrand presentation on UI driven designer UI
• Matias animations demo
• Higher order components
• Triage backlog
• China trip report

12/11

• Recap new renderer plans

• Dramatically smaller + faster
• Simpler design
• Better incremental compilation - faster builds
• Fully backwards compatible

• Build facade presentation
• Team activities

• Hike
• Board game night
• Night out in SF
• Escape room

• 2018 Conference Policy
• Angular 2017 Survey

12/4

• 5.1 Plan Review
• 2018 Planning
• Hiring
• GitHub bot
• Tree-shaking presentation

11/27

• Caretaker dashboard demo
• Stats review
• 5.1 plan (and what' in 5.2)
• Internal announcements

11/20

• [Manu] Process improvements

• New internal site for releases and process
• Dashboards on issue inflow/outflow + aging

• [Manu] Angular 5.1 release planning
• [Igor] Payload improvements shout out from AC
• [Rob] European Sharepoint Conference report

• Modern Sharepoint on SPFx
• Have been working with Sharepoint team on enabling Angular
• Lots of passion for Angular in the MS community
• Gave a talk in their Keynote on using Angular Elements to embed Angular apps
• Have a repo on the sharepoint org for driving community contributions
• Will have a team working on a CDK-based UI framework for Fabric-UI elements
• Angular Elements turns out to be a fine integration solution for current Sharepoint (pre-SPFx)

• [Jeremy] Caretaking sheet

• Created spreadsheet with appscripts to create a view of what needs attention

• [Igor] Productivity improvements

• Olivier's robot plan draft
• transition to bazel
• (later) CI improvements
• Caretaker spreadsheet

• [Igor] The Why doc

11/13

• Angular Connect Summary

• Very Positive
• Requests

• Runtime i18n
• Large project build time
• Growing List of issues and bugs

• Angular v5.1 Upcoming
• Material + CDK 5.0 Upcoming
• Misko Presentation - Faster, Smaller, Simpler Angular
• Animations Demo

• http://animationsftw.in

10/23

• External peer bonuses?

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

• Future of AngularJS support
• V5 planning

• Have an RC that may make final -- still validating
• Working on a place in the docs with upgrade instructions (v4 -> v5 and v2 -> v5)
• CLI v2 will bump to Angular v5 default

10/16

• Shipping v5

• Core has some bugs but no blockers
• Assessing issues in RxJS
• CLI has a size regression we're fixing
• Still need service worker integration with CLI for PWA

• AngularMix recap

• Announced Angular Elements and gave demo (publishing Angular apps as a Custom Element to embed in in non-Angular scenarios)
• Announced Angular Labs as label for stuff that is ready to test but whose API may change. Includes:

• ABC
• Component Dev Kit
• Schematics

• Community culture

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

10/2

• Q4 Planning

• TS/g3
• iv

• Shipping v5

• Taze rolled back compiler. Will try to re-land this week.
• Make CLI fast in watch mode. Current tsc ~2sec. There's some bug where they recompute too much.
• PWA is fixing bugs. CLI option is in the works.
• Issues with RxJS.

• AngularMix conference

• Jeremy, Igor, Alex E, Alex R. have reviewed presentations.
• Some others (Brad, Misko) need reviews.

• AngularConnect conference

• Going along swimmingly

• DevRel report

• Met with MediaCurrent last week showing sub-teams things about Angular

• Scoped Services design review

• Addresses how to lazy load services independent of root module or routes
• Adds new injector 'import' feature that lets you load services by stub/proxy that resolves at runtime when used

Sept 25

• Angular Elements design review

• Angular is currently good at consuming custom elements but there's no way to easily create them from Angular components
• Could serve as lower-surface way to start in Angular by just creating reusable components as custom elements

Sept 18

• V5 plans
• Amadeus visit next week

• Feedback on how Angular works at Amadeus
• Requests for changes and feasibility
• Future plans together

• Regressions in 4.4
• Presentation planning for AngularMix
• Q4 Planning

• Cleanup
• Infrastructure improvements
• Angular Elements
• Runtime i18n
• Error messages
• New arch design (ngState, etc.)
• Docs improvements
• DPG Partnership

• Interns planning season! Get your requests in this week.
• 2018 OpEx planning - DUE NEXT WEEK

Sept 11

• Follow up from team offsite

• Rolled up some feedback into 2018 Strategy Doc
• Social calendar coming soon
• More feedback to process...

• Blockers between here and v5

• Core: Making ngc faster, few other fixes, targeting 2 weeks
• Material: Migrating g3 from md- to mat- & other fixes. Targeting 2 wks to RC
• CLI: Just waiting on faster ngc to see if AOT will be default or optional

• Demo in-browser AOT example (aka AOT Plunkr/CodePen/etc.)

• Goal: Online editor that runs AOT in browser so fokls can create and share Angular apps
• Useful in examples, submitting bug reproductions, etc.
• Using the Monaco editor
• Live compiles in AOT
• Demo stores app source in a gzipped url for sharing securely - no server
• Created as a service we hope gets integrated in other online editors (we don't want to compete)
• Needs: Optimizations, bug fixes, some UX work
• Demo is at edit.ng (not for prime-time, no expectations that this will be for real use)
• Source github.com/adeora/playground

• Demo CLI refactoring prototype

• Goal: read your code, allow querying and transformations across Ts, JavaScript, CSS, etc.
• Code name 'arborist' (ha ha)
• Demonstrated querying functionality across source languages
• Plan is to use inside CLI first to reduce complexity and code size
• Plan to later release as generic functionality for automated refactoring tasks for anyone

• Reviewed design doc for the TransferStore API for Angular Universal

• Low-level API providing a key-value store you set up on the server becomes available in client
• Higher level API for rehydrating a HTTP cache on the client base on data queried on the server using the low-level API
• Providing a richer DOM API on the server using Domino
• Work is in progress, nearly done, but needs security review.

August 28

• Say hi to Joey - new team member on Angular Material

August 14

• Updates on v5 release plans

• PWA support to make building performant apps easier

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

• AOT by default coming to CLI with new watch mode - requires TS 2.4

• Offsite plans for next week
• Material and Core sync

July 24

• Abhi demo of AOT Playground app

• Web editor for Angular apps that supports AOT in browser
• 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
• One use will be for folks to create minimal reproductions for Angular team to work on with bugs
• Now using Monaco editor from VSCode
• Plan to show externally in early September

• Core tracking towards v5

• For the first time we're doing resource planning...with Gantt charts!
• Moving team-productivity items to after v5 RC (sigh)

• Material 2 tracking toward Final

• Moving much functionality to the CDK
• Doing full accessibility audit
• Ensuring all components use OnPush and can server-side render
• Audit on API consistency
• All bits tracking GREEN

• Travis issues

• Seeing lots of flakes this week
• Maybe linked to the Chrome driver

• Metrics update

July 17

• CE Demos
• Ensuring no new features in v5 RC.0
• Offsite reminder: August 24 & 25th

July 10

• Q3 OKRs big things:

• Smaller/faster: better optimization, smaller libraries, CLI does PWA by default
• Simpler: Able to use AOT for everything, simpler HTTP, simpler docs
• Easy v4 to v5 update

• Size update

• Now graphing size for angular.io
• Better JS optimizer in flight for the CLI

• Angular Material branding

• The "Material" team now supports many things

• Material Design components suite
• Component Developers Kit
• Flex Layout engine

• Seems like the team could use a name that's inclusive of the full set of products
• Brad thinks docs should fall under angular.io/docs rather than material.angular.io...TBD

• Angular team going on offsite in August!  In Seattle.  Details TBD.

June 25

• Did Q3 planning discussion for v5 and surrounding support
• Testing: Destroying fixtures on each test
• Demo: Service worker (arick)
• Demo: Tree (tina)

June 19

• Angular Material: md- vs. mat-

• Currently have mat- prefix to allow Angular Material work with AngularJS Material
• Proposal: move all Angular Material to move to mat-
• Would remove some size
• Could create tooling to auto-upgrade

• Timeline planning for Angular 5

• Current dates:

• RC in mid Aug
• Final in mid Sept

• Will publish roadmap for what's included

• Regressions in 4.2

• Had a release for 4.2 with too many regressions for comfort

June 12

• No meeting due to NO MEETING WEEK

June 5

• Size improvement update

• Looking to change bootstrapping to drop reflectMetadata
• Working on a platform config to make this possible with size savings
• Working on a null Zone mode that makes upgrade to Angular easier

• Igor + Ionic report

• Spent last week with Ionic folks improving startup perf
• Reduced app startup by 35% without network
• Still more good things to improve...

• Q3 Planning coming soon
• AMP-PWA!

• Alex R. gave preso on vision for creating support for server-side rendered AMP apps that upgrade to PWAs...

May 29

• No meeting due to holiday

May 22

• I/O conference trip report

• Had two talks
• Great customer interactions

• AngularJS update

• Still doing bug fixes regularly
• On v1.6.4 - now syncing to Google
• Product is very mature - bugs are either very small or very new/zany ideas
• Doing regular patch release to get updates to folks
• There will be a v1.7 that removes deprecated items and bug fixes

• Angular Material update

• Released Beta 5 last week
• Included first version of DatePicker
• First PR on DataTable happened
• Did accessibility fixit last week - 7 PRs happened, more in-flight
• Getting more accessibility help from experts that will hit future releases
• Missed updating CDN for AngularJS Material 1.1.4 - coming soon

• Demos

• Alex E. on ABC

• Bazel TypeScript rules are now on GitHub for early access folks!
• Shipped demo app using Closure compiler - 34K compressed
• Have a few folks building using this externally
• Using non-Angular libraries is still a pain we need to work on

• Olivier on i18n conversion tool

• Generated IDs were previously fragile due to how we generated them
• Demo'd tool that automates allowing both old-style and new style IDs as easy migration path

• Animations

• Lots of animation feature goodness just hit in Angular 4.2 RC0
• Biggest request satisfied with this was for query()
• Easy to orchestrate animations in parallel and in sequence across route changes
• Now writing guide for docs site

May 14

• MS Build trip report

• Had a booth next to the TypeScript team - had amazing booth placement
• Rob did two tech talks on Angular - standing room only!
• Lots of big enterprise folks came to talk to us
• Every other question was "how do I upgrade from AngularJS to Angular?"

• Performance focus

• Code elimination
• Serving practices
• Lazy loading

• Offsite planning
• Demos

• Miles on Date Picker

May 7

• Demos

• Alex R on Http and PWA
• Hans on CLI Schematics
• Andrew on DataTable
• Rob on Firebase

• Metrics review (stephen)
• Reactive support (misko)
• New angular.io site - launching soon

• Rewritten in Angular w/ Material, Universal, and as a Progressive Web App
• Now supports previews per GitHub SHA
• New left-hand nav organization to make nav easier

May 1

• Fun external sites

• https://www.shopstyle.com on Angular using server-side rendering to be fast
• https://hayneedle.com using ngUpgrade with v1.3.9 and v2.4.3
• http://passport2017.ca/ on Angular for planning your next vacation :)

• Google I/O preview

• Doing 2 talks
• Alex/Jules talking about PWAs and state of Angular
• Stephen/Rob Dodson talking about Angular + Web Component
• Have a codelab built by Kiril on Firebase (built in Angular!)
• Have folks in the sandbox tent to chat w/ Angular team

• Next week we're at Microsoft Build

• Rob doing a theater session
• At a booth in the Microsoft area
• Jules doing a Channel9 session with Anders
• Working with ASP.NET team on templates
• Talking to VS team about integration

April 24

• Docs plan - doing an overhaul over the next few months

• Simpler, more flexible navigation
• Make content less verbose and more focused on task
• Paths for beginner vs intermediate/advanced developers

• 3pty lazy loading

• Mechanism needed by UIRouter and other use cases
• Currently route token only available in Router package
• Need a general means of code splitting for use beyond Router that works in CLI
• Looking into this now...

• Reactive development in Angular

• Lots of folks using ngRx
• Need docs / best practices and possibly API support to make it easier
• Doing design review soon...

• Bundling/tree shaking tools

• All current tools assume they're the last assembler in the pipeline
• None of the tools are composable (they assume they're last) and none of them do everything we want
• Possibly want a universal bundle format and tools that know how to work on it

April 17

• AngularJS CDN versions

• Need to clean up our page for angularjs 1.x
• Reducing listed versions to last stable in each major (1.2.27, 1.3.17, 1.4.12, 1.5.11, 1.6.4)
• All versions will still be served, but we want to make sure folks use the best sub-version of their chosen version

• 4.1 plan

• Plan is to ship on May 5
• Nullability support and Animations bits are on track

April 10

• ngConf debrief

• Great vibe from folks excited about Angular v4 improvements
• Many banks there with booths by CapitalOne and Schwab.  
• Overall just good press
• DevRel had HUNDREDS of conversations
• Animations and Language Service were things folks said they loved
• Docs came up as a barrier for lots of folks.  We need to simplify the learning journey.
• Library authoring guide was very well received.

• Starting internal X-team Angular Platform group to contribute to components, build, scaffolding, RPC, etc.
• Q2 OKRs approved, now planning for Q3 to get us to v5.0

March 20

• Angular 4 release

• 4-5 blocking issues
• Most have PRs in flight
• On track for final release on Thursday 3/23

• Q2/Q3 planning

• Estimation and planning happening over the next two weeks

• DevRel update

• We can do better at triaging issues
• Will to build internal dashboard to better surface status

• CLI release

• Also plan to release final this Thursday 3/23
• Will default to Angular version 4

• Internal TypeScript conference happening next week

March 13

• Secondary owners

• Getting secondary owners for all critical components
• Misko now secondary on Forms
• Tobias on language service
• Jason on Router

• Breaking vs user pain impact

• Want to be clearer about what we incorporate into major vs minor releases
• Every change has potential to be breaking -- for example, folks may rely on bugs and fixing that bug may break folks.
• Suggestion is not that we change any commitments, but focus on user impact of every change
• Related: Example of very helpful commit message

• V4 progress

• Few outstanding pieces of work
• Reviewing regressions
• Igor doing primary triage
• Component authors should do secondary

March 6

• v4 Planning

• Fixing final bugs
• Getting doc done
• Just 2 more RCs planned before final

• Screenshot testing demo

• Material team created infrastructure for doing screenshot diff
• Goal is to prevent visual regressions
• Provides automated CI service that automatically fails when images differ outside the threshold

• v5 Planning

• Working through ideas
• Want to be locked by beginning of April

February 26

• External reaction to v4 RC.0/1

• Worked hard to eliminate breaking changes from Angular v4
• Both inside Google and externally folks appear to love the RC.
• Highlights for folks include improvement in speed, size, Service Worker support, packaging improvements, all with low to no cost upgrade.
• Now getting feedback from early adopters.  Busy fixing a few bugs.  Will want broader sets of folks giving feedback later.
• CLI received lots of positive responses as well - coordinating the releases was very well received

• Planning for Angular v5 this week and next.

February 13

• V4 update

• Primary change is new rendering pipeline making apps faster and smaller
• Making bundles work better for Webpack
• Will cut another beta this week and RC.0 next week

• ngUpgrade + Zones

• Working on a plan to make better performance for apps on AngularJS and Angular through ngUpgrade by making zones smarter
• Scrolling is currently one of the big areas impacted
• Plan is to throw errors for pathological uses
• New zone release this week to fix some other bits, but doesn't affect public API

• Material

• Landed namespacing change so teams can have both v1 and v2 components in the same app
• Rolled this change out across Google without issues

• CLI

• Planning to go RC.0 right after Angular v4 RC.0
• Created 'eject' button for folks who want to export for Webpack management
• Can now create apps using Angular v4.  This will be default when Angular goes to RC.

• Universal

• Main API to render to string is going in today
• Squashing bugs to get to RC.0

February 6

• DevRel Trip Report: MN

• It was very cold
• Stephen spoke at AngularMN meetup and GDG DevFest. Demo of upgrade for 2.6 (and how easy it is) won a lot of fans.
• Visited some of our partners/customers and local community. Discussion of pain points and issues.

• RxJS Contributor Days Report

• Igor and Rob attended. Report from discussions.

• Material Update

• Released 1.1.3 last week

• A4 Schedule & Release

• Status report from Igor.

January 30

• Long Term Support planning

• Have been talking to many enterprises who don't have ability to upgrade as often as we make major releases.
• 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.
• Currently deciding the details of how 'long' long will mean and what types of fixes.

• Branding

• Last week blogged that we prefer 'Angular' for v2.x+ and 'AngularJS' for v1.x
• We've made this change throughout everywhere we can find in docs, wiki, etc.

• Service Worker release

• Just pushed new build today v0.8.0
• 50% smaller!
• More stable & reliable
• Get it at @angular/service-worker
• Intention is that this becomes part of Angular CLI in March/April as part of the Angular v4 release

• Had 1 hour outage on angular.io last week

• SSL cert expired
• Wrote a post-mortem
• Reviewing with team tomorrow

January 23

• New process for design docs. Jules gave a quick overview of review process we'll be using moving forward to make doc sharing easier.
• Update on size/performance [Misko]

• 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're working on closure integration and tree shaking to further optimize compilation of angular code via closure.

• CLI

• Tight focus on performance, build time, rebuild time, and documentation for 1.0 release to support the next angular major release.
• We'll have a beta branch after that similar to other angular projects.

January 9

• Japan trip report

• Visited Tokyo and Osaka
• Had good press interviews
• Open source is a new concept in Japan corporations
• Very much wanted docs localization

• China trip report

• Photos (sorry, internal only) https://go/angular-gdd-photos
• 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).
• 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.
• Localization for docs is very important. It was really helpful to have support from local engineering teams on translation at our events.

• New approval and design doc process
• New launch review process
• Q1 Goals

December 19

• I18n

• Browser polyfills for i18n are in poor shape - buggy and missing features
• Missing features are particularly big in custom formats for dates and such
• There's a better feature set coming in ES2017.  Polyfil for this is also buggy.
• We'd like to recommend folks go on the new ES2017 polyfil
• AI: Naomi will reach out to ES2017 champions to see if we can help with the bugs.

• 2.4

• Includes patches and update from RXJS RC to current
• Plan is to release 2.4.0 and 2.4.1 this week
• No planned releases next week due to US holiday schedule

• It's just Angular

• We've been calling our current project "Angular 2" for two years now
• The "2" is no longer useful as SEMVER means we'll be upgrading our major version 2x / year
• Our hope is that folks just refer to the current project as "Angular" rather than "Angular 4", "Angular 7", etc.

December 12th

• We skipped our December 5th meeting as many folks were traveling
• Much of team is in China or Japan at conferences this week
• Igor's EU trip report

• Folks report majority of new projects in Paris area happening in Angular 2
• Spoke at ng-be about Angular 4 to help folks understand major releases are low-stress events -- blog post with details coming soon
• Ng-be was small but an AMAZING event for everyone involved

• Angular 4.0

• We have a breaking change coming so we can get on TypeScript 2.x (d.ts file format isn't backwards compatible)
• 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.
• Working on tooling to automate whatever breaking changes we can, even for obscure cases

• Naming of Angular

• We'll be dropping the version number when talking about Angular
• 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.

November 28th

• Mozilla will lift ban on Angular 1 plugins on December 1st.
• Angular versions 2.2.4 / 2.3.0-rc.0 going out this week

November 21st

• Angular Service Worker Update

• angular/mobile-toolkit beta in 2016

• Angular Universal Update

• Moving into angular/angular anticipating @angular/universal
• Building platform-universal (render to string)
• Working on core architecture
• Performance optimizations

• Material Update

• On track for beta in 2016
• Autocomplete is in development pipeline
• Working on hybrid Material 1 & Material 2 on the same page
• @angular/flex-layouts coming soon

November 14th

• CLI Future Plans (in discussion - not official)

• Transitioning to toolkit instead of just command line interface
• Existing projects with large scope needs what we have in the CLI but being called by a different tool chain
• Plan to create a toolkit with local development tools, static analysis, refactoring support, build, code gen, and deployment bits
• New CLI would be a shell over this new toolkit
• IDEs would use the toolkit bits as needed
• Proposed Roadmap:

• CLI 1.0 Final
• Refactor CLI project into SDK tools
• Create refactoring tools (auto-upgraded apps to vX to vX+1)
• Addon support
• Library support
• Custom Templates
• Future work (client/server architecture, etc.)

• Igor's Trip Report

• Went to Reactive Conf in Bratislava

• Gave talk on how we think about building frameworks and influences on how we created Angular 2
• Talked about Cypress e2e testing framework - Julie/Igor will investigate more vs what we're doing with Selenium
• Many misconceptions about performance

• Folks wonder if we use vDOM (we don't)
• 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)
• Lots of desire to get Material Design for Angular 2 to stable

• Spoke at Devoxx in Belgium

• Stephen spoke about Mobile
• Igor talked about why folks should consider Angular 2

November 7th

• Core

• Focusing on making AoT easier to use, better errors, faster
• Focusing on making Ionic apps faster as a first use case as it pulls in several third party libs
• Creating summaries so folks with build tools can do incremental AoT builds
• VicB will take over Router from VictorS
• Animations are now working with Web Workers
• Misko is restarting Zones work to ensure AsyncAwait works with it

• 2.2 Release

• Going out this week
• Two significant features

• AoT ngUpgrade support - dev guide will lag the release
• Ng2 Router support to help migrate Ng1 apps to Ng2

• Other minor incremental updates going in

• CLI

• CLI is near RC0
• Validating features and bugs list
• Will release as soon as validated
• Next focused on build time reductions

October 31st

• Project prioritization for 2017

• Speed + size reductions
• Better faster build tooling
• Easier Ahead of Time compile
• Support for all manner of mobile development

October 24th

• Many folks traveling to ngEurope
• Welcome Miles to the Material team
• Firefox blocked extensions written with Angular 1 due to security worries

• This does not appear to be Angular related
• We're working with the Firefox team on convincing them to revert their block

• Angular team hackathon update

• Several team members took two days off to build Angular 2 apps
• Goal was to learn things we'd like to improve in developer workflow
• Kara built a bill splitting app

• Found that preventing default on forms could better
• CSS is still hard :)

• Vic worked on our Periscope app (github issue prioritization tool)

• Pretended we were external folks evaluating widget libraries
• PrimeNG looked very nice, but ended up on ngBootstrap as it works with AoT today
• Created an autocomplete widget to learn how it could work
• Found some minor issues (captured for fixing) but overall was fun
• Wanted to have reusable page objects / mocks from the component library vendors to make testing easier

• Browserstack

• Can't get responses to our issues from any channel
• Looking into alternatives

• China trip planning

• Doing a team conference roadshow in China late this year
• Going to Beijing, Shanghai and possibly other cities

• Angular Universal update

• Started as community run project, but we're now heavily contributing from Angular core team
• Moving the core platform node part to the angular/angular repo so it stays up to date with any ng2 changes
• Next will be to improve the developer experience and potentially make changes to the platform server

October 17th

Agenda:

• Welcome new team members Tina, Miles and Andrew on Angular Material Team!!!
• What's up with Angular 2 inside google

• Much adoption internally - 50+ teams to date
• Several public teams launching soon
• Adding improvements to ngUpgrade to encompass needs of ng1 projects

• Continue priorities discussion

• Reviewed existing packages and projects we maintain
• Solicited priorities from each package owner
• Summarized needs of developers inside/outside Google

October 9

Agenda

• Hot topics:

• Angular 1

• Whether to provide opt-in ng-input-range for 1.5
• Moving internal teams off Angular 1.4
• Syncing angular 1.6 for internal use (1.6-rc.0 is planned for this week)

October 3

• Angular Connect was awesome!

• Talk videos are up on YouTube. DevRel working on a blog post.
• Lots of interest around AoT, Migration/NgUpgrade, CLI.

• 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.
• Kicking off issue queue triage this week, Igor to send email to the team with components.
• Hot topics

• Process, Launches, etc (Igor, Vic)

• Closed 300+ obsolete issues post Angular 2 Final
• Considering to use GitHub projects to assist planning and visibility

• Update from DevRel (Jules)

• Overwhelming number of enterprise customer requests have come in since final
• DevRel folks will be on planes for the rest of the year helping folks get going and/or be more successful with Angular 2
• Any team speaking plans need approval from Jules before committing.
• Planning an event in Japan for late this year

• Error messages and user pain (re: https://github.com/angular/angular/issues/12044 https://github.com/angular/angular/issues/7481 and others)
• NgUpgrade and AoT docs

September 12

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

• This addresses Webpack + Lazy loading plus Docs in IDE issues

• Material Design work update for this week:

• Theming
• Design doc for Select
• Strategy to avoid conflicts for apps migrating from Material 1

August 29

• Two blocking issues in RC6

• Detecting invalid elements.  Getting working for internal projects and then will be done.
• Repackaging ng2 core.  Just upgrading to the latest version of TypeScript but have found errors and will consult with the TypeScript team.

• Post RC6

• Core team switches to bringing API docs in line with latest changes
• Mobile team works on bringing version up to work with ahead-of-time compile

August 23

• Core Status

• Caretaker is gatekeeper until we release
• Animations tests found an IE11 memory leak issue introduced by Proxy zones fix. This was resolved late Monday.
• Deprecated API removal: PRs are ready to merge now that IE11 issue is fixed.
• Bundling strategy: Rob still working on this with Misko.
• RXJS upgrade: done in #10648
• I18N: validated now against some test applications. Xliff is in.
• Router: one PR pending to address CanLoad/CanActivate bug.

• NgModule on Large Projects feedback - Rob is fielding questions on #10552
• Validation of RC6 planned for this week.

August 15

• Core Status  - RC 6

• Caretaker is gatekeeper until we release
• No RC6 shipping until all deprecated APIs are removed.
• Peer dependencies issue between zone.js and angular versions. Need a decision on how to communicate or fix. [Igor, Rob]
• G3 is in sync with master. We have 8 PRs pending waiting to merge into master, testing now. (9 including the new zone.js)
• FakeAsync - expect to have fix in master EOD.
• 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]
• Bundling strategy: Rob has a proposal that needs approval, creating a github issue to describe it. Hoping to make a final call EOD Tuesday.
• RXJS upgrade: working on this today, will land with RC6.
• I18N: xliff and a few ngc improvements pending. Initial support is in master.
• Router: working on RC6 updates for lazy loading, bugfixes.
• Forms: Test updates PR pending.

• 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.
• Hotel deadline today for conferences. Talk to Jules if you got mail from her.

August 8

• Core Status  - RC 5

• Top SHA in master addresses remaining NgModules implementation.
• Caretaker is gatekeeper until we release.
• Ames validation and internal tests pass
• No blocking docs issues
• NgModules is complete in master. This is the last piece of the core API.

• Plan for remaining 2.0 releases after RC5 --

• post-RC5: No further breaking changes in Router, Forms, and I18N before 2.1.
• post-RC5: No further breaking changes in Core before 2.1. New features in animations, I18N, and Forms only. Bugfixes OK.
• RC6: removes all deprecated APIs (planned: at least 1 week from RC5) and we assess I18N and Forms API and Animations for final.
• We'll assess RC6 readiness at next week's meeting.

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

August 1

• NgModules update

• The core PRs for the proposal (from last week) are in master
• We are now working out details of lifecycle hooks and testing API for NgModules
• First look at a PR for lifecycle expected this Tuesday Aug 2

• NgModules Validation

• Material: Uncovered an issue related to Zones exposed by NgModules (Julie will help)
• Ionic have an issue related to metadata extractor (fix coming today)
• Firebase typings d.ts issue for Periscope (Rob to help)
• Rob has a PR for Angularfire that should unblock remaining ngc issues
• G3sync should be back in sync with master by Tuesday EOD

• Core status - RC5

• NgFor issue resolved.
• ngc metadata elimination (not blocking) [Alex E]
• Bootstrap best practices final (Igor)
• Sync Tuesday morning.

• Material

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

• DevRel update

• Working with Polymer team on ensuring Polymer/Angular works well together
• Presented at NodeSummit on the Evolution of Javascript

• Blog posts this week

• Rob working on an NgModules post for review
• Jeremy working on a Material update
• Intern blog post is coming

July 25

• Deep dive on NgModules (formerly App Modules)

• Misko presented the current state of the @NgModule proposal. (See doc at http://g.co/ng/modules)
• We are agreed that PR 10164 will soon be ready to merge into master so folks can validate against it.
• Open issues - for discussion via the shared @NgModules doc. Please add them at the bottom or in Docs Comments.

• 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)
• Deprecation strategy & decision for legacy bootstrap
• Tree shaking

• Naomi to schedule a mid-week check-in for core team on @NgModules

• Core status

• No RC5 this week. Focus is on proving out @NgModules in master.
• Matias is working on getting NgFor + Animations issue resolved
• Rob working on a blog post on @NgModules

• Validation plan for NgModules. This issue lists items that must pass before @NgModules is final.
• DevRel Update

July 19th

• No RC5 this week as we're validating some new bits.
• Docs localization projects are under way! See which languages have started building teams here.
• Core

• App Modules

• This is how components get compiled now.  
• Defines the metadata Angular needs.
• The old way will be deprecated for a migration period.
• Working to validate the current implementation this week against Ionic, Periscope, Ames, and other apps and libraries we maintain.

• Next SF meetup is August 3rd

• Stephen Fluin talking about App Modules

• MTV meetup is tomorrow

• D3 with ng2
• Angular Universal
• Ng1 http patterns lighting talk

July 11

• 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.

• AIs:

• Router to add warning messages
• CLI to add warning messages (lint)
• Core improved error messages from type checking
• Documentation to prepare folks what they can/can't do
• Sample app that shows how this all works together

• Router - Now v1 feature complete.  Lazy loading, guards, etc. works.  Release will come after RC5.  More docs in the works to help with adoption.
• 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.
• Security - Now have green-light from Google Security review team.
• 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!
• 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.

• AIs:

• ID experiemental APIs that must be stable by final
• Update example of using new recommended bootstrapping for RC5

• 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.  
• Validation of working with:

• Mobile
• Material
• Periscope / Ames
• Partners
• google3

June 27

RC4 Milestone - Meeting Tuesday to review status.

• Jeff (VicB) Query Param Encoding
• Igor work on public API cleanup, testing, platform browser
• Kara work on Forms

• RC5 Milestone

• Animation issues
• Offline Compiler
• I18N
• Forms

• Router

• Beta this week. One remaining change is in flight.

• Material

• Alpha-6 this week. One issue with Angular RC3 to resolve first.

• HTTP

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

• Periscope App

• Matias is adding Animations

• CSS Parser
• No team meeting July 4th, Holiday in the US.

June 20

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

• Early feedback from the community is positive
• Some good issues filed on new APIs, working through these now

• RC3 Goals

• Address performance regression and animation issue noted in RC2
• Bug fixes from early RC2 feedback
• Igor is lead
• Release notes: Stephen

• RC4 Goals

• Clarifying the public API surface (what's stable, what's private) and making sure it's correct.
• Testing API improvements
• Forms
• Offline compiler

• Remaining for 2.0:

• Review our APIs for final
• Offline compile
• Testing
• Docs and Dev Guide updates for new APIs (Forms, Security, Router, Offline Compiler)

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

• Animations (Matias)
• Material (Jeremy, needs help from Alex)
• Packaging (Rob)
• I18n (VicB)
• Tests (Misko)

June 13

• RC2 - tasks

• Finish minification/rollup work (Igor)
• Get last PR on Forms in (Kara)
• Release notes prep (Stephen)
• Docs to go with
• [goal/non-goal?] Offline compiler CLI - TBD later today.

• Forms update (Kara)

• Upcoming API improvements based on feedback
• Opt-in to new changes possible in RC2 once this last PR lands

• Router update (Victor)

• Alpha shipped last week (see notes below, two blog posts)
• New alpha coming this week with improvements based on community feedback

• Minification/Rollup update (Igor)

• We're going to preserve the approach using platform browser / platform dynamic
• We'll need more tooling to support other approaches. Still in consideration but not for RC2

• Milestones - planning recap (Misko)

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

• Angular 1 outage and sync

• We pushed a commit that broke the docs site because of flakiness on the CI server
• It’s fixed now by rollback. Pete is working on root cause so it doesn’t happen again.
• Igor needs help on the v1 sync to internal. Alex E volunteers as tribute.

• Welcome Jason

June 6

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

• Working towards RC2

• 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.
• Ran into issues in several places and needed to back-out some changes to get it working.
• Will release as soon as we can resolve these.

• Making several API/conceptual improvements to Angular 2 Forms for final, described in this doc.
• Latest Router revisions going live in a breaking change this week.

• Available on npm in @angular/router 3.0.0-alpha.2
• Announcement blog post
• Deep dive details

• Adding xliff format to our i18n/localization support.

May 31

• RC2

• Aiming for next week on Monday
• Reviewing API surface for gaps in docs generation
• Deprecating platformBrowserDynamic

May 23

• Progress towards final

• Finalizing Router feedback.  Now aligning the code.
• Animations landing in core this week.  Docs coming with this as well.
• Externally usable support for the template compiler in the next week or so.
• Cleanup on API docs coming together (several private APIs are public when they shouldn't be).
• Focusing on bug burn-down and getting PRs in for final.

• PR process

• Have been getting on top of the PRs
• Got ~70 in.  Down to ~100 open.

• Angular Material

• Releasing Alpha 5 this week (tabs, slide toggle, grid list)

• I/O recap

• Progressive Web Apps talk went spectacularly.  Rob & Alex showed off our end-to-end solution for PWAs.  Nearly 7K views on YouTube already.
• Appears that video for Cross Platform Angular 2 by Jules and Kara was lost.  Big bummer, but was standing room only in the tent.
• Addy Osmani of the Chrome team developer relations gave a talk on Progressive Web Apps Across All Frameworks.  Was generally very good and Angular 2 showed off spectacularly in the performance numbers.

May 16

• Working towards final release across teams

• Critical bit is in getting template compiler and tree-shaking (Rollup.js or jscompiler) working in the Angular CLI
• Core team focused on it this week

• Router

• Incorporating feedback from many folks on the latest changes in the release candidate
• Validating the APIs against a growing sample app from the docs
• Talking with the ngRx router folks as they're very similar

• Animations

• Finished last bit on leave-animations
• Likely to hit MASTER next week
• Next functionality will be on replacing inline-styles with classes and key-frames

May 9

• Ng-conf recap (Naomi, Misko)

• Blog posts coming from Jules and Rob.
• Press/PR queries
• Team retrospective Wednesday

• What's needed for I/O presenters?

• Need a stable release to npm with template compiler latest before I/O
• Alex E has a PR with bugfixes. Review by Vikram / Igor please.
• Closure support would be nice but not blocking. Possibly EOW.
• CLI: Hans needed for some CLI fixes (pair with Jeff)
• Material: Jeremy needed to release with offline compiler support. (pair with Rob)
• Would be nice to resurrect per-SHA releases with new packaging. (Igor)

• Caretaker this week (Igor)

• Martin is caretaker, but in an unfavourable time zone. Chuck J is the caretaker from Wednesday.
• Priority for internal should be landing the template compiler CL.
• There have been some out-of-order SHAs merged in, which complicates the sync.
• Vikram has repackaging tool updates, ts2dart updates, waiting to go in.
• Will resolve the plan for internal user sync mid-week when full team is back in office.

• What should land for the next RC?

• I/O is Wednesday next week, if we want an RC before then.
• Should include new template compiler fixes, web worker support.

• Anyone blocked or urgent?

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

• Amadeus report

April 25

• New compiler

• We've split the packages to accommodate the new compiler changes
• Now trying to consume them from a real app to test tree shaking
• We can build the app, but tree-shaking via Rollup.js is not working properly
• Working through this right now

• Animations

• Animations now working with code gen in the new compiler
• Now working on tests and examples

• Router        

• New router core works, end to end should work by end of the week
• Will need docs updates, will sync up with Ward

• CLI

• John Papa made several suggestions that we'll address in the next few days
• In last bug bits to get stable version ready
• Working on an upgrade path to take folks from one angular release to the next (or any number of future releases)

• Progressive Web Apps

• Demo app to be done by EOD tomorrow
• Has App Shell and Service Workers
• Based on Angular-CLI
• Will be creating an app manifest plugin as well
• Will be creating Cookbook Recipes in the docs for folks to build their own

• Docs

• Have landed changes to API doc styles that make them easier to navigate and use
• Will be adding tags to docs to indicate STABLE vs PREVIEW release status
• Blocked on the repackaging PR landing in master

• Test

• Have new async and fakeAsync test wrappers that handle errors much better -- all external folks should be using this now
• Have template caching for tests so you can use fakeAsync with external templates
• Have fixes for test component builder that will hit the next release (not today's)
• Adding helper methods to trigger events better
• Hooking up unit tests with ngZone so we can wait for components to stabilize before we continue in the tests

• Release

• Did not release last week as we're working through the new compiler changes
• We will cut a release today

April 18

• Core

• Change #1 for offline compile is in MASTER (see last week for details).  Coming in this week's release.  
• Rob created a minified gzipped version using Rollup.js that weighs in at ~45K -- smaller than Angular 1!  
• We believe we can do better using jscompiler...working on this now.
• Tobias now working on Change #2 that will allow more dead code elimination.  May be code complete this week.

• Animations

• Now working on code generation to work with Core Change #1.
• Will be usable after this lands.

• CLI

• Integrated latest style guide changes.  Will track this as it evolves.
• Will be creating optimized deployment build path based on Change #1 this week.  
• We'll no longer use bundles from the CLI.

• Progressive Web Apps

• Will have app and build path that checks all boxes for Progressive Web Apps by end of this week
• Has reasonable fallback for Safari using AppCache until they implement Service Workers
• The smaller framework size makes Time To Interactivity timeline get smaller.

• All

• Working on presentations for ng-conf

• Changes based on new bundling for offline compile

• We'd been assuming folks would have to use bundles to deploy apps.
• Now that we have a real path to payload reduction, we have other options.
• http/2 won't have the performance needed for a while now, so users will need to generate minimal deployment compiles on their own
• Two paths to this are jscompiler and Rollup.js.
• Rollup requires ES6 input.  Jscompilier can use TypeScript as input via our Sickle tool.
• Rollup does this via modules and jscompiler uses types.
• 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.
• The Angular CLI will be able to build with these inputs and build the right optimal version for developer deployments.
• 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.
• We will provide tooling (npm module for WebPack, etc.) for our component authors.

• Several guest blog posts coming this week:

• React Native - Marc Laval
• Meteor - Uri Goldshtein
• Auth with JSON Web Tokens - Ryan Chenkie

• GitHub permissions reorg

• We've recently reduced owners for our GitHub repo to just our tech leads.  Let us know if you're broken for any reason.
• There are many old repos under angular that we'll be deleting if they haven't had recent activity.

• Merge status

• Folks are unhappy with how long it takes to get their PRs in
• It's invisible to external folks when their PR needs testing against all the Google apps -- this can take some time to resolve
• Maybe need to do a blog post?  Add more info to CONTRIBUTING.md?
• Also just need to make this go faster :)

April 11

• Core

• Two changes in the works, the rest is bug fixes and minor improvements.
• Change #1: 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.
• Change #2: The way we bootstrap host views is changing so that we can do tree shaking and eliminate dead code in final builds.

• Material 2

• Has a plan with 4 milestones to get to an Early Access edition
• Just released milestone #2
• You can track the milestones in GitHub

• Docs Site

• Adding bunch of content before ng-conf
• Adding "why Angular?" Content
• Adding better docs landing page
• Adding several sub-domains like mobile.angular.io, universal., etc.
• Just pushed new developer guides on DI, dynamic forms, component interaction, and component styles

• Tools

• Style Guide: John Papa is leading style guide development with Minko Gechev and others.
• Angular CLI: Currently implementing the style guide into our blueprints.  Will integrate offline compilation next.
• Batarangle (rename pending): 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.
• Language Services: 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.
• ngLint: 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.

• Router

• Working towards some API changes in time for Final
• Will automatically do code-splitting/lazy loading based on Routes if desired
• Simplifying several concepts and APIs to reduce confusion
• Resolving some critical corner-case bugs

• Animation

• Near integration time for the new animation library.

• I18n

• Template string extraction and pluralization directives complete.
• Several more minor steps required to make it usable in real projects.
• Requires completion of Change #1 in Core to work.

• TypeScript @ Google

• Have first sets of teams shipping to production.
• Working on integration with other developer workflow infrastructure this quarter to complete the full picture.

• Mobile

• Goal is to make it easy for developers to create Progressive Web Apps on Angular 2
• Well under way to show this via a GitHub management app
• Plan to have seed/CLI starter tools by ng-conf and Google I/O presentations
• Will have a mobile.angular.io sub-site to help folks get going

• Marcy Sutton

• Will visit tomorrow to chat about a11y and will give a talk on a11y the Mountain View meetup
• Has been working on an a11y cookbook chapter with Almero Steyn

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

April 4

• BUILD conference update

• Staffed our booth 3 days.
• Gave away many shirts. :)
• Awesome conversations with many folks using Angular 1 and Angular 2.
• Brad gave a standing-room-only talk on Cross Platform Apps with Angular 2 (slides)
• Misko and Brad and Anders (TypeScript lead) gave an interview for Channel 9
• Evan and Rado gave two talks on how we're making TypeScript work with our existing Closure compiler

• CLI

• We can now uglify files for minification
• Will start bundling soon with SystemJS
• GitHub deploy is ready

• Material

• Will likely publish an Alpha 2 with lists and inputs today

• Router update

• Simplifying and refactoring the router
• Merging 'instruction' with 'componentInstruction'
• Will probably drop 'name' and just have URLs so we can automate lazy loading
• Are simplifying aux routes and making them just routes.  They will behave in the same way.  The default route just has a blank name.
• 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.
• All Routes are async routes which will aid in lazy loading.

• Angular 2 debugger

• Now highlights which elements were affected in the last rendering/data update
• Merged graphs to show injectors, routes, and components in one diagram

March 28

• Walk-through final spreadsheet

• Updated

• Bubbling up changes to the master CHANGELOG

• Last week we shipped three things (router, views and zones) that weren't in the changelog
• How should we fix this?
• Seems to be some kinds of bugs in the CHANGELOG script
• Jeff Cross will look at this in the next caretaker and send backfill features

• Update on directory structure

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

• Ng-conf presentations

• Confirmed plans with everyone

• Router plans

• Focused on the issues
• There are some critical issues, but not too many
• There are some documentation issues that will solve many things

• Angular 1

• Need other googler to help do the syncs

March 21

• Angular 2 final tracking doc review

• Went through the milestone work with each contributor

• Directory structure

• 5 years ago we created angular-seed for angular 1
• 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 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
• 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're optimizing for developer ergonomics rather than tools

• Release policy

• Working on consolidating to a single version of Angular 1 at Google
• Will be down to 1 version of ng1 at end of the month
• Have a strategy and plan where we'll have STABLE and HEAD for ng1 and ng2
• HEAD will be only for a small whitelist of folks who want to be on the edge
• STABLE will receiive no breaking changes
• We'll have office hours for migrating from STABLE to STABLE+1 twice a year.

March 14

• Rangle.io update on Batarangle

• Now using new API from Angular 2 (beta 8) to publish changes rather than using mutation observers and have gotten much greater performance
• Demonstrated new Router and Injector tree tabs that give visual relationship diagram for your app (super hot!)
• 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)

• Tracking towards Angular 2 final

• Code generation

• Producing the generated code (Tobias)

• Has a PR 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.
• Will have a phase-2 that's smaller that re-does bootstrap and component loading.  

• Doing the metadata extraction to feed to tools (Chuck)

• Metadata writer for files with d.ts files - green just needs to be merged
• 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

• Combining these into the build tool (Alex Eagle)

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

• Material 2

• Alpha 0 landing this week
• Button, card, checkbox, progress circle, sidenav and toolbar
• Further release will contain more :)

• Gestures

• Kara has a design doc on how we plan to address
• For Material 2, we're thinking we may write our own
• May be possible to use Hammer -- will chat with Misko to talk more

• Working on guidelines for how we publish to NPM

• We need to be coordinated
• If someone is using all of our components, they should do it the same way
• Need to make a decision now
• Researching scoped packages to see if this is the right path

• Pro: We own a namespace that nobody can name-squat on our package names
• Con: The '@' symbol looks strange in imports and may not work for some

• Update from Fluent Conference

• Brad gave a keynote bit.  Please watch and give him feedback as it contains our core messages for the year.
• Alex Rickabaugh gave talk on Progressive Web Apps on Angular 2 (video coming)
• Rob Wormald gave talk on Reactive Angular 2
• All talks were very well attended and received much Twitter love afterwards
• Folks seem to have heard our messages and have less worry and FUD about upgrading

• Blog posts: Kara will have first draft this Friday
• Angular Edu (internal)

• Working on an externally sharable version of our Google Angular 2 training
• (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
• Zones

• Want to move Zones to TC39 stage 1
• Will standardize the minimum feature set for v1
• Node folks are wary of things that looked like the domains feature they did so we're backing away from this for now
• Will have fork(), run() and wrap().  Errors will be forwarded to the global error handler.
• Phase 2 will have zone delegates that allow interception of error handling.
• Will work with WHATWG to get the scheduling piece
• TC39 meeting is March 28th

• Method parameter decorators for ES6

• Contributor sent PR to BabelJS
• If they accept, Angular 2 in ES6 will be on par with TypeScript experience

• Error handling

• Working on low-hanging fruit - runtime type checks to give clearer messages
• 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.
• Have several PRs on the way to improve several situations

March 7

• Supporting focus on polish.  What would help?

• Plan ahead for focused work on themes
• Create maturity stages for features
• Build more apps ourselves
• Better system around github issue tracking

• Prioritization app
• Rotation role
• Automation

• In the chute for Angular 2 final

• Have built tracking spreadsheet
• Please update status and add github tracking issue by end of the day
• Plan to publish these as a milestone on github so external folks can track

• Angular 1 caretaker rotation

• Needs more ability of folks who can sync to google (currently only 3 folks can do it)
• Angular 1 release has been blocked on google sync for 1+ month
• The Plan:

• Igor and Matias will work on getting current release out
• Reduce load with automation - Igor to prioritize set of tasks
• Combine sync role with other Angular team caretaker to expand total pool of folks who can release

• Common approach to benchmarking

• Many teams need the same type of benchmark service
• We should consolidate on a common approach
• Biggest issue is creating an environment where others can take the benchmarks and reproduce the results
• Travis is possibly good enough, at least for now
• Goal would be that perf numbers can be compared within a batch
• Will also start a Google Compute Engine
• Also there is webpagetest.org that has normalized machines
• Jeff/Rob will own and report back weekly

• Blog posts

• Alex doing one on offline HelloWorld
• Rob doing one on Progressive Web Apps and on Modules
• Jeff to do one on our vision around Mobile
• Matias on our parsers - template, css, html, expression
• Hans on CLI
• Kara on beginner success factors and trackby
• Victor wrote one about advantages of Angular 2 templates

Feb 29th

• Update on Batarangle from the Rangle.io folks

• Recently added:

• Cyclic component search
• Clicking on component sets scope in Chrome console in $a
• Redesigned info panel with broken out Properties, Dependencies, Input, and State
• Dependencies have click-through that shows all other components that have the same dependency
• Editable tree view is alpha, but coming along nicely (needs PR from Tobias - merging this week)

• Tobias: Would be nice to be able to jump to instance of the provider
• Can download now from batarangle.io
• Will reach out to Ward to add cookbook/other docs
• Rob: Would love you to reach out to Pascal Precht to integrate visual change detection
• Alex: Would be nice to click on a component and trigger an event AND be able to see who subscribes to events
• Submit issues at https://github.com/rangle/batarangle/issues
• Ward: Would be nice to have a feedback mechanism integrated into the tool as well
• Router tree, component tree, injector tree would be nice to all see visually

• Recap from the planning offsite

• Spent two days talking about long term plans
• One big ambition around making angular 2 future-proof with free upgrades
• Other ideas around greater tool ecosystem visual designers, etc.

• Build infrastructure and continuous improvement

• Last week we spent much time fixing and disabling flaky tests
• We've had much trouble getting to a green PR state
• Planning on a test-jail process to rehabilitate them out of the main build
• Sauce labs is currently VERY flaky

• Seems XHR related - seeing timeouts

• Need to have a way to prioritize PRs for merging
• Problem is that it's hard to make it through the merge queue

• Milestone plans

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

• Router update

• Brian is on vacation - please pull in Naomi/Igor for needed coordination
• There will be incremental changes, but no dramatic breaking changes
• Will get:

• static link checking
• canActivate
• Async module loading through router (though this may happen after final)
• More router transparency

• Other note: UI Router is now working with Angular 2!

• Status of the PR queue and releasing

• Last week we were out for part of it
• Focused on build issues
• We're behind, but are working on merging the backlog this week

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

• 150K domains now have Angular 1 on them
• 200M documents have Angular 1 in those pages

• ng1 sync and versions in g3

• Have a long running project to move everyone to Angular 1.4
• Making much progress, but now there is Angular 1.5
• Angular 0.9.16 is still in use though! :)
• Desire would be to coniuously upgrade Angular 1 to current stable
• Need to create policy of upgrade expectations
• Also need to time cutover
• Naomi/Igor/Martin will create policy tomorrow

• ngAnimate.x in google3 and One Version Rule maintenance

• Prototoypes hitting angular 2 in a few weeks
• Key features:

• Annotation-level JS DSL
• CSS Parser
• Sequencing
• Web Animations

• Dramatically less code required
• Separates styling from animation sequencing

• Simplifies code
• Lets us make much higher performance animations
• Much less DOM manipulation required
• Fewer recalculation, many fewer function calls
• Can just write staggering bits in JS without touching the static CSS bits

• Using Web Animations API

• Supported in Chrome and Firefox
• Edge and Safari require polyfill
• Guarantees compositing that eliminates reflows
• Is static, but our CSS parser lets us do choreography atop it
• May create a smaller replacement for mobile as polyfill is 12K

• No need for getComputedStyle that we do in ng1 animations
• Still working on testing story

• cancelling animations
• knowing when animations are complete
• ability to turn off when doing integration testing

• Tobias: Would be interested in creating an explicit grammar for IDEs and other tools
• Will talk to Marc to see how we can map this to React Native
• Basics should hit master in a few weeks

[Meeting hiatus for 2 weeks for holiday and team planning offsite]

Feb 8th

• Payload reduction "progress"

• Alex started on offline template compilation
• Please take a look at the 10K doc and see if there are items you'd like to take on
• Rob notes that the rollup.js folks got Angular 2 building last week.
• We've set up both Angular and Angular+Hello World sizes with various bundling strategies to track progress

• Popularity report (Brad)

• Angular 1 holding stead with 1M+ developers
• 292K 30-day actives on angular.io docs
• 120K Twitter followers
• 70K 30DA on blog
• 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.

• PHP rendering update

• We expanding the Angular Universal effort to support PHP-compatible server-side pre-rendering for existing PHP backends.
• It's early days, but we are making good progress thanks to volunteers from the community.
• Igor met w/ GDEs working on PHP/Drupal integration
• Have several proof of concepts of server-pre-rendering, i18n, etc.
• Meeting with Drupal team later this week to find out what's most important to do next
• So far going very well with no real issues

• Template services plan

• Bill T. on TypeScript team built a prototype (background description, implementation) of Angular language services in TypeScript for intellisense supported by tsd
• Goal is to give anyone building an editor/IDE Angular completions/error checking for free when using tsd
• Working with TS team on a plugin API for this so others can do this as well
• Next steps are to port the prototype to the plugin API
• Working on a new approach that uses the Angular compiler as well

• Preview of the offsite

• Busses will come from SF and MTV
• First day is around vision, team dynamics, and group dinner, games following
• Second day is for breakouts on sub-teams and long-term plans

• Angular 2's HTTP moving to it's own repo

• Easier to maintain and build tooling around issues if this is a separate repo
• Moving HTTP out of the core repo (thanks to tool from the Dart team!)
• Will publish separately on different schedule from core Angular 2

• Electron

• We want to fully support building desktop apps via electron in Angular 2
• Rob + Matias will move Rob's electron repo into angular/electron

• Events

• Addes 2 new events to angular.io/events (DEVOXX and DotJS)

Feb 1st

• React Native update from Marc

• Have been exploring using React Native with Angular 2
• In all code is in mlaval/poc-angular-react-native
• Built a kitchen sink app to explore features, widgets, components, etc.
• Scroll views, menus, inputs, swipe and other gestures, alerts, Android intents, native platform APIs, integrating web views, etc. all work
• Brought this all together with the ToDo MVC and uses local storage
• 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
• Demonstrated native animations like the button ripple effect
• Angular 2's http works giving a nice path to reuse logic from other Angular apps
• Built a simple animation integration with fairly smooth results - 60fps on modern phones
• Did a crazy demo where he put the ToDoMVC app into many bouncing balls in the screen - they all remained responsive
• Summary is that it seems ready to build real applications
• Tobias: did you try the layout animations (native animastions) like CSS3?
• 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.
• Brad: What does it need to be even better?
• Marc: Certainly needs more tests.  I'd want to see many higher level components with TypeScript types, etc.
• Jeff: What about iOS?
• 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: One thing is that not every UI component has a bridge.  You will likely need to wrap with native code for things.
• Igor: Would it be possible to create a generic bridge like NativeScript has?
• Marc: I'm not sure.  
• 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.
• Brad: It's also fine for this to be a differentiating feature between the two offerings.
• Marc: Next, I'll be building some high level components and extensions to see the developer experience there.

• Angular 1 focus areas

• Feature roadmap won't have anything major.
• Most of the work will be in supporting folks in migration to Angular 2.
• 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.
• We'll capture migration guidelines and helpful practices from these.
• There will likely be other tooling we create.
• The new Component Router will be going out this week for ng1.
• Support for the new i18n and Animations are coming as well, but we need to do work on the timeline.

• Angular 2 weekly releases

• We have many issues and pull requests that we need to address.  
• Plan is to aggressively merge and fix these.  
• We'll start triaging and assigning work after Monday meetings.
• Wednesdays are dedicated to just fixing issues.
• New Angular 2 releases should come out each Wednesday as well.

• Successful on call/caretaker rotations

• Caretakers need to do two roles

• Triage and issue escalation for each team:

• TypeScript
• Core
• Protractor
• CLI
• Material
• Mobile

• Merging and cutting release

• Long term idea is that all projects are run via Angular CLI
• Until then, there will be manual work to do things the same way
• Need to synchronize the labels and rules for triage

• AngularConnect and ngEurope

• They are close together in Sept and Oct
• This is Brad's fault and he's sorry
• Most of the team will be at AngularConnect

• Building remodel update

• We're moving upstairs in July

• Offsite

• Please respond with availability by Tuesday

Jan 25th

• Demo of the new Dart Dev Compiler for the team

• Meant to improve the developer lifecycle
• Allows for incremental (file-by-file) cycle for non-Dartium browsers
• Compiles to ES6
• Use Babel/TypeScript/Closure compiler if you want compilation to ES5
• Requires code with stricter type checking
• Produces more readable compiled code for when you're debugging

• Update on i18n support

• Goal is to translate templates to multiple languages
• First working on static messages - current work is on extracting static messages in the next two weeks
• We'll generate one version of the application per locale
• Next phase will be for dynamic scenarios like gender and pluralization

• Router update

• Working to make lazy loading / code splitting work with Component Router to make it free or nearly free based on your routes
• May just be a slight tweak to existing syntax
• Developing in the next few weeks

• Angular 1.5 update

• Plan is to release RC2 on Wednesday
• Will do 1.5.0 final the following week or a week later if big issues
• Working with Brian to ensure the Component Router works well
• Main feature is the component helper that lets folks build apps in the Angular 2 style and use the Component Router
• Will include overhaul to PhoneCat tutorial to match the component API
• Also includes a dev guide section on component helper

• Animation Update

• Design doc has been created
• Goals/tasks have been documented:
• The CSS Parser is close to completion
• The next areas of ngAnimate will be un blocked once the parser is in

• Mobile update

• Finished our first iteration last week
• Published first alpha of AngularFire 2

• Will be presenting this Wednesday at the Modern Web UI meetup

• Created first cut of a reference app to show off Progressive Web App features

• Server rendering
• Service workers
• Web Workers
• HTTP/2

• Angular 2 release plan

• Plan is to do weekly releases from here to final

Jan 25

• Quick demo of Angular2 on DDC (Dart dev compiler)

Jan 11

• Tim presented "How Angular 2 transformer for Dart works"
• Moved Angular 2 to MIT license based on developer feedback/requests

• Matches most other JS projects
• Details on blog.angularjs.org

• Grand plan for 2016

• Launch ng2 final (material design components, more perf, less payload, docs, animations, etc.)
• Mobile

• Progressive web apps are blazing and amazing
• Native well integrated with all ng2 ecosystem services
• Both fully integrated with Angular CLI for provisioning, testing, deploying, etc

• Desktop install infrastructure (via electron.js)

• Run Angular within Node, leveraging Web Worker-style separation
• Supporting development workflow within Angular CLI

• Long term performance plans

• Performance should be obviously fast and map very close to what you'd write by hand
• Audacious goal of 10K payload size for Hello, World

• Reboot the web build system
• More to come

• Update on Angular 2 vs Angular 1 traffic

• 1.06M 30-DA on angularjs.org
• 210K 30-DA on angular.io
• 19.8% of visitors now on ng2, up 10% Q/Q
• Some overlap is assumed

• Mary Poppins Chatbot status update

• Goal is to automate all our processes through the robot on Slack/GitHub
• Currently broadcasts build status
• Commands are hosted in github.com/angular/backend-bot

• Material Design for Angular 2

• Core contributors doing design planning
• Will have screenshot diff tool to ensure rendering fidelity between releases
• Much investment in performance test infrastucture
• Working on key deliverables for Angular Material 1 as well

Jan 4

• Post beta.0 (and post ngmaterial 1.0) check-in and what's next? (Brad/Igor)

• Improving speed and size (payload)
• Addressing feedback on the Beta (in particular Forms & Router)
• Material components for ng2
• Expanded TypeScript support inside Google
• Canonical ng2 training materials
• Finishing dev guides and ensuring tests run on all API/example docs
• plus more bits listed below...

• ng-merry-cleanup 2015 (Igor)

• Igor and others created doc on cleanup projects we've always wanted to do
• Goal is to improve our internal productivity
• Some is still left and should get done in the coming months
• Big pending change is npm3 migration (#6067, #6213, npm/npm/#10380)

• Interactive Mary Poppins (Matias)

• We have a useful GitHub robot on Angular 1 called marypoppins
• Want to have this for Angular 2 as well, and even upgrade feature set
• Investigated Hubot and Lita as infrastructure options
• Both seem to have identical features
• Leaning towards Hubot given less code required, direct integration with GitHub, and team familiarity with JS vs Ruby
• Current thinking is that all repetitive tasks should be automated

• Caretaker (Igor)

• Need to ensure that folks on rotation are in MTV
• Cannot be an ad-hoc task, cannot be something done while traveling

• The Journey to 10K (Igor)

• Goal is to get Angular 2 Hello World app in under 10K payload size this year
• Critical for addressing mobile 2G cases
• Angular should be very small for small apps and pay only for what you use for larger apps
• Should give developers clear insight into what import choices mean to final delivery size
• Current size is 164K (angular2.min.js + dependencies)
• Goal for Q1 is to get to ng1 size ~50K

• Angular Dream CI (Igor)

• Current CI system is very poor in many ways
• Wrote spec for an efficient, reliable system
• Some aspects include sharing build artifacts, parallelizing work, coordinating VMs, debugging support, etc.
• Doc to be public soon

• Analytics (Igor)

• Goal is to optimize Angular core team processes better in 2016 via data analytics
• Currently collecting analytics from our build system, GitHub activity (PR created/merged/comment/etc), and payload size
• Available in graphs within Google Analytics

• pre-TC39 briefing (Igor)

• Igor/Misko/Brad met with Yehuda and MS folks on TC39 proposals we care about
• Plan is for us to help more on bits we care about in Decorators
• More work coming in support for Zones and Module Loader

• Even faster Angular 2 (Tobias)

• Currently landing several performance optimizations
• Soon landing offline compilation to further improve startup time and reduce payload (don't need to ship the compiler with this)
• Now planning to generate dependency injection as well.  Further reduces payload size and improves performance.
• In particular, much faster on VM cold start scenarios.
• Results will be easy to show via generated code as it looks like what one would write by hand.
• Will continue to work via online code generation for developer workflow.
• Debugging should get better as you an now set breakpoints where divs are created.  Could even create breakpoints in HTML templates.
• Generates less code than we previously did with the offline compilation so very large apps can scale better.  Small apps will pay less.

Dec 7

• keeping remote contributors in the loop (Igor)

• Igor:

• We've been moving quickly in the past few weeks on ng2
• Remote folks have trouble staying current when much info happens in conversation
• We want remote folks to be at the same level as others in the office
• Part of it is to be aggressive when you need attention
• But what about when you don't know you need to know new decisions?

• Julie: would like to see Slack used more aggressively
• Jeff: GitHub is often better than Slack as it withstands time better than Slack
• Igor: It's hard with the many opinions that can occur on GitHub
• Jeff: It's better for documenting rationale rather than discussion.  Slack is for the discussion.
• Tobias: I think what's really missing is the bits in the daily standup meeting.

• Animations demo (matias)

• Targeting Beta 1 or Beta 2
• Solves 95% of issues we have with ngAnimate 1
• Current CSS code is verbose and not reusable
• Can be slow when you have lots of style sheets - currently drives folks to JS-animations
• 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)
• Designed to be compatible with Web Workers

Nov 30

• beta check in (Igor/Brad)

• mostly on track
• lifecycle hooks prefixing is ready to be merged
• kebab-case removal is almost ready - we are working on tooling to migrate existing templates

• angular-material (Naomi)

• IE11 issues with flexbox - might affect 1.0 release

• update on Mobile (Jeff)

• 3 person team formed
• working on prioritizing work

• measuring impact to decide what matters the most
• angular universal and service workers are at the top of the list

• Static vs Dynamic and Toolability (Martin / Tobias)

• Toolability is important for Angular 2
• when creating apis, think - can we statically analyze the code (imperative+declarative) and understand it? If not, tooling will struggle.
• we will soon start working on deamon that will expose all statically analyzable info to IDEs and other tooling

• Benchmarking update (Igor)

• working with Paul Lewis on setting up independent benchmarking infrastructure
• Paul is exploring our benchmarks and benchpress

• Weekly updates for g3 (Igor)

• we'll email updates every week after the ACX meeting

• cli update (Igor)

• Ciro (GDE) and other volunteers have picked up some tasks and are making good progress.
• 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)

Nov 16

• lifecycle hooks - short update (Naomi)

• Wrestling with the options for how to avoid name collisions
• Will resolve this directly after the full team meeting
• 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.

• beta-00 check-in and completion times (Igor)

• Packaging has pending PR.  Igor will review and (hopefully) merge tomorrow
• Router: Matias helping Brian land the big refactoring this week.
• Parser: Vic has the PR ready -- merging in the next few hours.
• Lifcycle hooks: TBD later today
• Per-commit npm/pub: Good enough for Beta
• Per-commit sync: Has flaky tests to deal with.  Plan is to ignore flakes and have folks fast fix.
• Router binding from host to child:  PR ready to go when test for aux route completes.
• Public API review: Will have % complete numbers tomorrow.  Targeting 11/17.
• Source maps: Pawel will start tomorrow.
• Bundle/barrel reorganization: 50% complete.  Targeting landing on 11/20.
• Router docs: Ward is close on Angular 2 version.  Needs Brian to review.  Pete will start helping on Angular 1 version.
• RxJS size reduction: Down to only adding 6KB.  Want to go lower.  Talking with TypeScript and RxJS team about further options.  

• PR queue

• Igor will review green PRs and get to merge status.

• g3sync status

• we are back to the new normal. when a PR is ready to merge, add the "merge" label.
• igor will review the internal owners file to avoid collisions like we ran into this week.

• GDE summit this week - please accept your RSVP in Cal

Nov 9

Agenda:

• AST Binding Transformations and Route Link DSL

• If you want to write a link in routing you have to write an array of strings+objects
• This binding transformation would let us hook into how change detection builds up data structures and modifies them
• Having it for the Beta would be desirable
• Victor would like to make it more generic so it can handle more cases of parsing many styles of templates
• Alex R. has a prototype of this for generic templating
• Victor thinks it will take a few days
• Making it work with transformers and offline may be tricky
• Need to worry about IDEs.  Integrating with our compiler would make this work.
• Victor + Alex will work on this next week.
• Plan is to only expose Router usage initially.

• Deprecated APIs will be removed after Beta
• Now at around 50% towards API documentation goal

• Alex + Igor are assigned
• Moving plunkr examples to the new docs system

Nov 4

Agenda:

• OKR review - focusing on beta, deprioritizing some non-Beta items
• New rotation! THE CARETAKER (Igor/Jeff)

• Spreading system maintenance and monitoring to a rotation program across the whole team
• Rotation will last a week
• We’ll have a set of improvement tasks that you’ll do instead of your regular work

• PR queue: who reviews this week? what about community PRs?

• Need to return to this post-beta

Nov 2

• Short meeting. Real meeting will be Wednesday.
• Igor has a spreadsheet with broad categories of issues in the beta-00 milestone.
• All work should be happening in the beta-00 milestone (if you're working on something else, clarify)

October 26

Agenda:

• When is Beta?  The short list is:

• Break into sub-modules so we have a reasonable packaging story
• Finish docs
• Fix bugs

• Beta includes

• Core
• Forms
• Router
• Other bits will come ASAP, but not required for beta

• Technical training kickoff

• Building internal Angular 2 training for Google
• TypeScript for internal is a bit tricky due to experimental status
• DanAnh joining group to project manage this
• Meeting tomorrow to kickoff course development

• Agree on packaging document.

• Will be splitting angular into sub-modules.
• Working to eliminate boilerplate for component imports...mechanism has several options.
• Both will happen for beta.

• Better commit messages => Better change log (Igor)

• Need more descriptive messages
• Will enforce our Angular 1 style

• g3sync update (Igor/Alex)

• 15 failures, 150 SHAs behind (mostly docs)

• Code structure more inline with Dart.

• Looks good.  To be done post-Beta.

• Automating npm publish to do per-commit releases (Igor/Alex)

• Plan to push nightly or hourly releases to npm
• Could happen after Beta
• Nice thing an external contributor could take

October 12

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

• Naming change bind() to provider()
• A few Rx changes making clearer APIs

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

• No breaking changes
• No major refactorings
• Nothing  wide-reaching functionality changes
• Fine to do bug fixes
• 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

• Most of team is practicing presentations for next week
• Moving to an API deprecation model for breaking changes
• Building infrastructure to push ng2 to npm (and likely code.angularjs.org) on every green SHA

October 5

• Demo: getting started faster when using TypeScript  (Alex Eagle)

• 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
• Changing the way we generate and distribute TypeScript typings
• Users will just have to npm install
• This will get everything set up without having to additionally configure IDE
• ‘tsc --watch’ also ‘just works’
• Also eliminates much work from our release process as we don’t need to generate them or push typings to DefinitelyTyped repo.
• More details on the extra work that will need to happen at https://github.com/alexeagle/angular2-distro/blob/master/README.md

• Module loader - recap and next steps [Victor]

• We’ve been experimenting with alternatives to System.js
• Aiming for zero setup required for users
• Planning to generate a commonjs bundle so folks can much more easily use Webpack
• Julie and Pawel working on this

• Docs status

• In API docs, just need Metadata and Test symbols documented
• In-docs test infrastructure to be merged later today
• Igor working with John Papa and Ward Bell on developer guide bits

• Priority this week:

• Triage issues from alpha-38 this weekend and prioritize.
• Can we cut an alpha-39 by Wednesday - bugfix only to unblock docs? Plan on alpha-40 for Friday will contain the di binding -> provider rename.
• 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.
• Freeze Angular 2 for Angular Connect docs and demos Friday. No breaking changes after that date. [Naomi to let presenters and docs know]
• After Angular Connect, we will revisit overall release process.

September 28

• Sync to Google Status

• Jeff broke the backlog sync of 250+ commits out into 1) rename and 2) other stuff, grouping into smaller chunks.
• 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.
• 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.

• Release Process (Release Notes, Documentation Updates)

• Customers (internal and external) are asking for more detail on what has changed between versions.
• 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.
• 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.
• 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.

• Triage of Issues Status: We are 100+ issues behind for triage. Need a more scalable process. Revisit with Misko.
• Animation DSL Status (Misko, Brad and Rob are missing … This will happen next week)
• Docs Progress Update

• Status of DevDocs/API and where we need help

• > 50% done, but still lots to do.
• Igor, Victor, Alex R, Matias, Rob W, working on docs this week.
• 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.

• New API Overview UI Design (Naomi showed early mocks for a map of Angular 2)
• 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)

• Martin and Alex, need to update grades on TypeScript effort.

September 21

• Removing traceur

• Originally, we used Traceur to transpile from AtScript (now TypeScript) to JS & Dart
• After much hard work, it is gone from our codebase
• Fully using TypeScript for all transpilation
• We may move from es6shim to core.js for ES6 bits (As do TypeScript & Babel)

• API docs progress

• Many core team folks focused on API docs last week
• 8% complete, additional 12% started
• Fixed many docs infrastructure issues first

• d.ts file wasn’t inline with the public API docs
• fixed public/private incorrect bits
• still many issues around how we present content we create content (creating links, function signatures, etc.)
• Came out with a list of issues we should process this week

• Want to have a good set in place for AngularConnect

• Have completed some of the biggest API docs
• Will prioritize APIs users hit in the first minutes of development
• Several of the first concept guides will hit then as well

• Compile as build step

• Goal is to dramatically improve startup time and reduce Angular 2 size
• Have created offline compiler pipeline tool
• Goal is to land this week in core
• Need to create tool that integrates with Angular 2 toolkit/CLI

September 14

• API Docs Authoring Sprint

• Brad has an API Author’s Doc which describes how to write API docs
• Rob Wormald to share his plunker setup with TypeScript loader and SystemJS
• Examples should be copy-pastable (including imports)
• Examples should be in CodePen; copy links into content; later we will single-click link to the CodePen example
• Version of Angular used in examples should be documented
• Team members will go through spreadsheet and self-assign pieces of API that make sense to them.
• Would be nice to throw TypeScript loader on code.angularjs.org (done)
• How will we test changes in a real UI as we go?

• Checkout angular.io, and symlink or copy built files from angular/dist
• Brian will make this easy and amazing
• Brian will temporarily document the process without the “ideal” solution

• Will create a special branch to push docs to

• NO CODE CHANGES ALLOWED!

August 31

• Transitioning from builtwith.angularjs.org to madewithangular.com

• Handing off curation and ownership of the Angular showpiece site to community-run madewith.angular.com. It's more current, and has good momentum.
• We'll deprecate the old site and direct folks to it. All the content still lives in the github repository.
• Blog post is coming. Brad will write it and introduce Jules to the folks involved.

• The team reviewed the angular 2 developer survey results.

• Some enterprise folks had difficulty accessing the survey from behind firewalls.
• Blog post will be out next week with the results.

• Continuing vision discussion. Brad presented.

• The importance of focus on "the first 20 min" for a new developer
• 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]
• Beyond that, what are the critical overall visionary goals for angular?
• How do we measure success against our stated goals?

• Update on ts2dart

• We discussed:

• Developer productivity
• Contributor experience
• Dart output quality

• Need conditional compilation (proposal coming) to get the code looking idiomatic for both language
• Some patterns that won’t compile cleanly can be caught in tslint
• Need to add this to our quarterly goals
• Need to document things we shouldn’t do in TS (top-level execution blocks, const semantics, etc.)
• Need feedback from external contributors on what they need to be successful

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

• Coordinating with Angular 1 changes

• Keeping Angular Material in sync with AngularJS causing non-trivial friction
• Will pin Material to AngularJS previous version (n-1)
• Going to add tests on AngularJS to catch more of the regressions

• Core Update [misko]

• Large raft of (minor) breaking changes we’ve made last week to rename things.
• Naming Conventions: TypeScript has set of naming conventions we’ll follow for the public API
• Breaking changes: 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.

• Want to get to “no more breaking changes in core” very soon
• This does not include http, router, etc.
• This is criteria for beta
• We still have Observable/Rx changes that we know are coming

• Sugar: Making many updates for more ergonomic/less boilerplate-y APIs to ensure better developer experience
• Upgrade: Can now bootstrap Angular 2 inside Angular 1.  Next step is to do the other way around.  Will then work on transclusion and injection.
• Presubmit: We now have presubmit details on our dashboard to make sure we stay on top of it

• Docs update

• Working on an Angular 2 Cheat Sheet - anything missing? Please comment.
• 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:

• Reusable components,
• Component communication,
• Navigation architecture (Router),
• Server communication,
• Debugging,
• Bootstrapping,
• Attribute directives.

• Ping Naomi if you can help.

• App Experience update

• Introduced use cases for Angular 2 last week
• Will break down most important ones, do scoring
• Testing: 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
• Animations: Rob + Matias doing Animations for Angular 2.  First version lands this week.
• Router: Brian working on managing multiple history stacks.  Working with Ionic folks on this.
• Bundling: Jeff aligning publishing with NPM and breaking Angular 2 into smaller sets.  Have some remaining bootstrap and Dart issues to work through.

• Tooling for Google

• Can now run Blaze build with TypeScript library
• Goal is to have Closure compiler be able to consume output

• Shadow dom changes

• Shadow DOM spec has changed to support the slot proposal.

• Blink (Chrome) will support both old and new syntax

• This change is easier to implement for browser vendors.
• Proposing that we support both ngContent and add ngSlot to support Shadow DOM for folks who want it.

• Proposal for custom event manager plugins. Needs discussion after the meeting so we can decide what the best approach is.

August 24

• Angular 2 Roadmap and Vision

• Reviewed for team as we head for Angular 2 beta
• Values: developer productivity and community
• Strategies:

• Angular1: low boilerplate, structure, testability
• Angular2: fast by default, simpler, remove architectural limits, mobile as first-class

• Will cover in detail at AngularConnect conference in October (London)

• A plan for ts2dart tooling

• Dart is evolving, and ts2dart should evolve with it
• We should be easing the burden of contributors who aren’t familiar with the dart build process
• Dart output should be idiomatic

• Revisit subteam alignments

• New teams were: core, application, material, tooling
• Going fine, let’s keep trying it out

• ts minify demo

• focusing on property renaming to improve minification over uglify
• first target is the ts2dart tool of about 2K LOC
• not currently renaming external symbols or class names
• Results of running both tsMinify and uglify against ts2Dart sample result in 56K vs original 72K (also uglified) for a 22% space savings!
• Final code will be gzipped as well
• Next target will be running it on Angular 2

• e2e use case coverage

• Maybe pick time near holidays to focus on non-feature work
• Other topics could be tooling, process, docs, etc.

• new angular 2 compiler pipeline that will be implemented soon

• Template compilation is our next target to make Angular faster
• In prototype, compilation got 8x faster and bootstrap (compilation + view creation) got 3x faster
• This prototype turns compile to a build-step
• Means production version of Angular could not ship the compiler code and become much smaller
• Offline compiler will also find errors and report them to command line or IDEs

• productivity issues
• User journeys

• Igor and others on the team have organized many “user journeys” describing how we expect users to interact with Angular 2.
• Team members are to review and add/edit journeys
• Sub-teams will use journeys as a means of communicating what’s being worked on weekly/quarterly

August 17

• AngularConnect

• Core team speakers and talks have been decided.

• Plans for browser support on Angular 2

• Proposing to add full suite of browsers to CI
• List of what we’d support:

• Firefox
• Safari (desktop + mobile)
• IE11, 10, 9
• Edge
• Chrome (desktop + mobile)
• Android (try 4.1.x+, fall back to Chrome if impossible)

• [Jeff] Review feedback and experiences from Utah hack night

• Aaron Frost sponsored an Angular 2 hack day in Utah last week
• Focus was on uncovering usability improvements needed for Angular 2 Beta
• Jeff and Misko joined remotely to help
• Themes of issues:

• Knowing how to use decorators properly
• Template syntax confusion (binding properties, bubbling, etc.)
• Quality of error messages

• John Papa likely to do a similar hack night

• Another hack day for ourselves to build Angular 2 apps

• Want to build deeper apps using many components working together
• Focus on the testing story completeness and ease-of-use
• Build for mobile
• Happening Sept. 10-11

• Subteams

• Our team is big, we should have some more focused sub-teams.
• Stand-ups are a lot of people, a lot of discussion isn’t relevant to everyone
• Our full team meeting should be focused on cross-cutting design reviews
• Possible teams

• Angular 1
• Internal google productivity
• Core (DI, compile, render, change detection, zones)
• Application (router, animations, i18n, persistence)
• Tools (various Dart tools, ts2dart, CLI, toolkit, etc.)
• Docs
• Material

• Next step: teams nominate their representative / rotation
• Stand-ups still happen at 11, but in sub-teams
• Brad to publish first list of who is in which team

• Next set of design reviews

• Pipes
• Persistence plans
• CLI
• Docs
• On push detectors
• Compiler overview + offline compile plans

• Yegor:

• ng2 google3 report: where we are today
• Main requests:

• Features needed soon: animations, i18n
• New features: User action timing tracking
• Wants more focus on reducing start-up time, particularly for mobile

August 10

• Process for managing issues for angular/zone.js, and allocating people/time to a few critical pending issues [Brian]

• Possibly pull the repo into the Angular 2 core process
• Misko will do the work to make zone.js issues show up in core dashboard
• Brian will document how this will work for zone.js contributors
• We'll add the process steps to TRIAGE_AND_LABELS.md

• AngularConnect planning for flights, talks, etc.