1
1
# Material Design for AngularJS Apps
2
2
[ ![ npm version] ( https://badge.fury.io/js/angular-material.svg )] ( https://www.npmjs.com/package/angular-material )
3
3
[ ![ Build Status] ( https://travis-ci.org/angular/material.svg )] ( https://travis-ci.org/angular/material )
4
- [ ![ Gitter] ( https://badges.gitter.im/angular/material2.svg )] ( https://gitter.im/angular/material?utm_source=badge&utm_medium=badge )
5
4
6
5
[ Material Design] ( https://material.io/archive/guidelines/ ) is a specification for a
7
6
unified system of visual, motion, and interaction design that adapts across different devices. Our
@@ -16,24 +15,14 @@ For an implementation of the [Material Design Specification (2018+)](https://mat
16
15
please see the [ Angular Material] ( https://material.angular.io/ ) project which is built for
17
16
[ Angular] ( https://angular.io ) (v2+) developers.
18
17
19
- ### <a name =" lts " ></a > Long Term Support
18
+ ### <a name =" lts " ></a > End-of-Life
20
19
21
- AngularJS Material has entered a Long Term Support (LTS) period which ends on December 31st, 2021.
22
- This date aligns with the
23
- [ AngularJS LTS] ( https://docs.angularjs.org/misc/version-support-status ) period.
20
+ ** AngularJS Material support has officially ended as of January 2022.**
21
+ [ See what ending support means] ( https://docs.angularjs.org/misc/version-support-status )
22
+ and [ read the end of life announcement] ( https://goo.gle/angularjs-end-of-life ) . Visit
23
+ [ material.angular.io] ( https://material.angular.io ) for the actively supported Angular Material.
24
24
25
- We now focus exclusively on providing fixes to bugs, in the 1.2.x branch of the library, that
26
- satisfy at least one of the following criteria:
27
- - We receive a report of, or detect, a security weakness which is then verified
28
- - A major browser releases a version that will cause current production applications
29
- to stop working
30
- - The [ jQuery library] ( https://jquery.com/ ) releases a version that will cause
31
- current production applications to stop working
32
-
33
- AngularJS Material 1.1.x will get a new version, if and only if, we verify a new severe security
34
- weakness.
35
-
36
- Learn how to report security issues
25
+ Find details on reporting security issues
37
26
[ here] ( https://github.com/angular/material/blob/master/SECURITY.md ) .
38
27
39
28
![ venn diagram] ( https://cloud.githubusercontent.com/assets/210413/5077572/30dfc2f0-6e6a-11e4-9723-07c918128f4f.png )
@@ -43,7 +32,6 @@ AngularJS Material includes a rich set of reusable, well-tested, and accessible
43
32
Quick Links:
44
33
45
34
* [ API & Demos] ( #demos )
46
- * [ Contributing] ( #contributing )
47
35
* [ Building] ( #building )
48
36
* [ Installing] ( #installing )
49
37
@@ -70,54 +58,6 @@ AngularJS Material supports the screen reader versions listed
70
58
- Or you can build the documentation and demos locally; see
71
59
[ Build Docs & Demos] ( https://github.com/angular/material/tree/master/docs/README.md ) for details.
72
60
73
-
74
- ## <a name =" releasing " ></a > Our Release Processes
75
-
76
- To preserve stability with applications currently using AngularJS Material, we do not follow semver.
77
- We have three types of releases:
78
-
79
- * ` major ` : major releases will be done in the separate [ Angular Material] ( https://github.com/angular/components ) repo.
80
- This type of release will not be used within AngularJS Material.
81
- * ` minor ` : contain breaking changes in addition to patch release changes.
82
- * ` patch ` : non-breaking changes (no API, CSS, UX changes that will cause breaks in existing AngularJS Material applications).
83
-
84
- ##### Patch Releases
85
-
86
- The patch builds (1.2.1, 1.2.2, etc.) are prepared based on commits in the ` master ` branch;
87
- which contains only non-breaking changes (I.e. bug fixes, new features, API additions, and minimal
88
- non-breaking CSS changes). We are targeting ` patch ` releases every 2 weeks.
89
-
90
- ##### Minor Releases
91
-
92
- The minor builds (1.1.0, 1.2.0, 1.3.0) can contain breaking changes to CSS, APIs, and UX.
93
- Our formal release of ` minor ` builds is much less frequent. The release process for ` minor ` builds is currently
94
- being re-evaluated.
95
-
96
- > For the purposes of AngularJS Material, you * could* think of the patch releases as being * minor* changes,
97
- and the 'minor' releases as being * major* changes according to semver.
98
-
99
- ## <a name =" contributing " ></a > Contributing
100
-
101
- Developers interested in contributing should read the following guidelines:
102
-
103
- - [ Issue Guidelines] ( .github/CONTRIBUTING.md#submit )
104
- - [ Contributing Guidelines] ( .github/CONTRIBUTING.md )
105
- - [ Coding Guidelines] ( docs/guides/CODING.md )
106
- - [ Pull Request Guide] ( docs/guides/PULL_REQUESTS.md )
107
- - [ Software Process] ( docs/guides/COMMIT_LEVELS.md )
108
- - [ Change Log] ( CHANGELOG.md )
109
-
110
- > Please do ** not** ask general questions in an issue. Issues are only to report bugs, request
111
- enhancements, or request new features. For general questions and discussions, use the
112
- [ AngularJS Material Forum] ( https://groups.google.com/forum/#!forum/ngmaterial ) .
113
-
114
- It is important to note that for each release, the [ ChangeLog] ( CHANGELOG.md ) is a resource that will
115
- itemize all:
116
-
117
- - Bug Fixes
118
- - New Enhancements
119
- - Breaking Changes
120
-
121
61
## <a name =" building " ></a > Building
122
62
123
63
Developers can build AngularJS Material using NPM and gulp.
0 commit comments