Skip to content

docs: update readme for Q1 2021 #21542

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 12, 2021
Merged

Conversation

jelbourn
Copy link
Member

We're still working on the same set of projects for Q1 2021 as we were for Q4 2020.
The bulk of our effort is going into rolling out our MDC-based components to our users
inside Google. This is the first phase of our MDC-component rollout; the second phase
will involve moving the components to our stable npm packages.

Fixes #21538

We're still working on the same set of projects for Q1 2021 as we were for Q4 2020.
The bulk of our effort is going into rolling out our MDC-based components to our users
inside Google. This is the first phase of our MDC-component rollout; the second phase
will involve moving the components to our stable npm packages.

Fixes angular#21538
@jelbourn jelbourn added docs This issue is related to documentation merge safe target: patch This PR is targeted for the next patch release labels Jan 11, 2021
@jelbourn jelbourn requested a review from mmalerba January 11, 2021 18:06
@jelbourn jelbourn requested a review from a team as a code owner January 11, 2021 18:06
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 11, 2021
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jan 11, 2021
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba merged commit b842891 into angular:master Jan 12, 2021
mmalerba pushed a commit that referenced this pull request Jan 12, 2021
We're still working on the same set of projects for Q1 2021 as we were for Q4 2020.
The bulk of our effort is going into rolling out our MDC-based components to our users
inside Google. This is the first phase of our MDC-component rollout; the second phase
will involve moving the components to our stable npm packages.

Fixes #21538

(cherry picked from commit b842891)
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Jan 14, 2021
We're still working on the same set of projects for Q1 2021 as we were for Q4 2020.
The bulk of our effort is going into rolling out our MDC-based components to our users
inside Google. This is the first phase of our MDC-component rollout; the second phase
will involve moving the components to our stable npm packages.

Fixes angular#21538
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement docs This issue is related to documentation target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update readme for Q1 2021
5 participants