search

Templarian / MaterialDesign

✒7000+ Material Design Icons from the Community
https://materialdesignicons.com
Other
11.02k stars 724 forks source link

RELEASED - Version 6.1.95 - Breaking Changes #5409

Closed mririgoyen closed 3 years ago

mririgoyen commented 4 years ago

Version 6.1.95 was released on Monday, September 6th, 2021.

We are now at the halfway point between v5 and v6, so I felt that it would be appropriate to have a single resource tracking all upcoming breaking changes that will be introduced in our v6 release. This issue will be kept updated as we get closer and closer to release and then will act as a reference.

Icons Being Removed (41)

The follow icons have been deprecated and will be removed entirely:

Icons Being Renamed (51)

The following icons are being renamed:

FAQ

When will v6 be released?

Version 6.1.95 was released on Monday, September 6th, 2021.

What's up with your version numbers?

We do not follow semver. Our version number indicates how many icons are available in the icon pack. However, we do try to lump as many breaking changes as possible into major version releases (so every 1000 icons). We aim to add approximately 100 icons per minor version release. We sometimes make breaking changes in minor version releases, so it is always important to look at our changelog when updating.

Sjoerd82 commented 4 years ago

How does this impact people that use Material Design icons via frameworks, like Vuetify?

Simran-B commented 4 years ago

@Sjoerd82 It's a breaking change. If you upgrade to v6 you will have to change the icon names in code, unless Vuetify provides a compatibility layer. That applies to renamed icons, for removed ones you can either pick another icons if there is a suitable one, or use a third-party icon set to fill the gap like http://simpleicons.com/ for brand icons.

Simran-B commented 4 years ago

Should we rename the face-woman* icons to face-female* for consistency? They are the only ones with "woman" in them, and we have none with "man" (well, except pac-man...)

mririgoyen commented 4 years ago

Should we rename the face-woman* icons to face-female* for consistency? They are the only ones with "woman" in them, and we have none with "man" (well, except pac-man...)

Let's open up issues for proposed breaking changes and leave this for a summary or discussion about the changes as a whole.

Simran-B commented 3 years ago

google-photos should be removed. We don't have the latest design (see #5293) and it's a brand icon anyway. The pinwheel icons will remain.

bootstrap should also be removed. They updated their logo with v5 (currently in beta, also see #5238) and it's a brand icon.

mririgoyen commented 3 years ago

I've updated #5293 and marked google-photos as deprecated. We'll leave bootstrap alone for now because it is a developer tool and that falls in the realm of our accepted icons. Consider it grandfathered in.

Templarian commented 3 years ago

I added a note to address finally dropping the other font files as suggested in this issue: https://github.com/Templarian/MaterialDesign-Webfont/issues/59

Going to take it one step further and only bundle Woff2 after 6.0 This means anyone targeting IE11 will need to use an older version. Almost all large companies are dropping IE11 support in 2021 so this is a good time for us.

digitalpoin commented 3 years ago

Please update car icon for "car door open"

mririgoyen commented 3 years ago

Please update car icon for "car door open"

@digitalpoin I'm not sure what you are asking here, please open a new issue if you have a request for a new icon or an icon update. Thank you!

digitalpoin commented 3 years ago

Please update car icon for "car door open"

@digitalpoin I'm not sure what you are asking here, please open a new issue if you have a request for a new icon or an icon update. Thank you!

Oh sorry. I am just suggesting to add an "open door car" icon in MaterialDesignIcons for the next version. Thank you in advance.

zgover commented 3 years ago

@goyney would you mind editing the original issue content—providing brief insights of the icon task list under 'Icons Being Removed'—specify either name of alternative or aliased resolution or just icon EOL decision. This will enable support for substantially greater consumer awareness while migrating; saving time, resources and energy by minimizing page navigations to the respective icon issue.

mririgoyen commented 3 years ago

@goyney would you mind editing the original issue content—providing brief insights of the icon task list under 'Icons Being Removed'—specify either name of alternative or aliased resolution or just icon EOL decision. This will enable support for substantially greater consumer awareness while migrating; saving time, resources and energy by minimizing page navigations to the respective icon issue.

This issue serves as that reference. Each linked issue contains more information if absolutely needed. The TL;DR is that we are deprecated and removing most brand icons and pointing people to SimpleIcons for brand icon needs. Brand icons carry a certain amount of risk so we are slowly reducing that surface area.

juhasev commented 3 years ago

I think we should take it easy on renaming and deleting icons. This is a major burden to update hundreds of icons currently in use especially the ones that got deleted.

mririgoyen commented 3 years ago

I think we should take it easy on renaming and deleting icons. This is a major burden to update hundreds of icons currently in use especially the ones that got deleted.

We do not make breaking changes lightly. However, when we do, we align them to the major breaking version change (in this case v5 ➜ v6). You are not required to update, but if you do, you will need to update any places in which you are affected by the changes. This is the case for nearly every piece of open-source software out there.

It's also important to note that we don't follow semver here. So, we literally amass breaking changes over the course of building up another 1000 new icons. This usually happens over the course of about 10 months, so when a major version comes, it's important we take our time.

Please use this issue as your migration path once v6 is released if you chose to upgrade.