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

Planning for v2.0.xx #1983

Closed
Templarian opened this Issue Apr 4, 2017 · 18 comments

Comments

Projects
None yet
5 participants
@Templarian
Owner

Templarian commented Apr 4, 2017

You know what would be fun, planning for v2.0.xx release.

While 1.9.32 was about renames/breaking changes. Ironically it's looking like the v2.0.xx should be a little less breaking.

Tasks

  • Naming fixes?
  • Drop IE8 Support. :before, ::before
  • Only include WOFF, WOFF2, TTF (included not used).

Icons

  • #180 - Calculator Icons
  • #263 - Image Editor Selection Types
  • #302 - Weight LB / g
  • #393 - email-box & link-box
  • #400 - Geometry
  • #409 - Flickr
  • #480 - piggybank
  • #521 - chess icons (with -outline variants)
  • #541 - Weather Icons - Review which are still needed
  • #561 - library-video
  • #1034 - GPU
  • #1323 - hammer
  • #1422 - Linux Distros
  • #1426 - EU Powersocket
  • #1578 - Playing Card Suits
  • #1858 - Starred List
  • #1913 - A Few Aliases
  • #1968 - Restore / reset icon

@Templarian Templarian referenced this issue Apr 4, 2017

Closed

Planning for v1.9.xx #1891

8 of 8 tasks complete
@MrGrigri

This comment has been minimized.

Show comment
Hide comment
@MrGrigri

MrGrigri Apr 4, 2017

Collaborator

I believe for issue #1422, we should only include the most common. And according to Distrowatch, the top 10 for 2016 were:

  • Mint
  • Debian
  • Ubuntu
  • OpenSUSE
  • Manjaro
  • Fedora
  • Zorin
  • elementary
  • CentOS
  • Arch

And of corse, we must take into account those icons that will not look recognizable at a 24x24 size.


: Distrowatch

Collaborator

MrGrigri commented Apr 4, 2017

I believe for issue #1422, we should only include the most common. And according to Distrowatch, the top 10 for 2016 were:

  • Mint
  • Debian
  • Ubuntu
  • OpenSUSE
  • Manjaro
  • Fedora
  • Zorin
  • elementary
  • CentOS
  • Arch

And of corse, we must take into account those icons that will not look recognizable at a 24x24 size.


: Distrowatch

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Apr 4, 2017

Owner

@MrGrigri / Others feel free to edit my comment to extend the list with bullet points.

Owner

Templarian commented Apr 4, 2017

@MrGrigri / Others feel free to edit my comment to extend the list with bullet points.

@PeterShaggyNoble

This comment has been minimized.

Show comment
Hide comment
@PeterShaggyNoble

PeterShaggyNoble Apr 10, 2017

Collaborator

Added #521 & #1323.

Collaborator

PeterShaggyNoble commented Apr 10, 2017

Added #521 & #1323.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Apr 12, 2017

Owner

If we drop IE8 support complete which kind of is the plan for the next version... I think we can drop all the other fonts than woff / woff2 / ttf.

Over on the official set @Pomax wrote a good write up here on why it's probably a good idea.

We're really going to be targeting Bootstrap v4 realistically going forward and even that is IE10+ (we'll have IE9+).

Owner

Templarian commented Apr 12, 2017

If we drop IE8 support complete which kind of is the plan for the next version... I think we can drop all the other fonts than woff / woff2 / ttf.

Over on the official set @Pomax wrote a good write up here on why it's probably a good idea.

We're really going to be targeting Bootstrap v4 realistically going forward and even that is IE10+ (we'll have IE9+).

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Apr 12, 2017

Owner

He's right we could drop legacy mobile versions also and leave out ttf also. Need to look into that, unfortunately I don't have stats to see who still really uses that.

https://css-tricks.com/snippets/css/using-font-face/#article-header-id-1

Owner

Templarian commented Apr 12, 2017

He's right we could drop legacy mobile versions also and leave out ttf also. Need to look into that, unfortunately I don't have stats to see who still really uses that.

https://css-tricks.com/snippets/css/using-font-face/#article-header-id-1

@JamesCoyle

This comment has been minimized.

Show comment
Hide comment
@JamesCoyle

JamesCoyle Apr 12, 2017

Collaborator

I use TTF to install as a system font.

Collaborator

JamesCoyle commented Apr 12, 2017

I use TTF to install as a system font.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Apr 12, 2017

Owner

@JamesCoyle https://materialdesignicons.com/design You want the design download, not the webfont. This is released after every version also.

Owner

Templarian commented Apr 12, 2017

@JamesCoyle https://materialdesignicons.com/design You want the design download, not the webfont. This is released after every version also.

@JamesCoyle

This comment has been minimized.

Show comment
Hide comment
@JamesCoyle

JamesCoyle Apr 12, 2017

Collaborator

Ah so there's still a TTF available. I'm all for getting rid of the TTF webfont. Personally think it's time to abandon IE and anything before Android Lollipop (though best to support KitKat too).

Collaborator

JamesCoyle commented Apr 12, 2017

Ah so there's still a TTF available. I'm all for getting rid of the TTF webfont. Personally think it's time to abandon IE and anything before Android Lollipop (though best to support KitKat too).

@PeterShaggyNoble

This comment has been minimized.

Show comment
Hide comment
@PeterShaggyNoble

PeterShaggyNoble Apr 13, 2017

Collaborator

Anything that helps kill off IE gets my vote! 😆

Personally, for the benefit of those who do use it as a system font and may not be aware of the design resources page, I'd like to see the TTF still included in the download, even if it's not in the CSS.

Collaborator

PeterShaggyNoble commented Apr 13, 2017

Anything that helps kill off IE gets my vote! 😆

Personally, for the benefit of those who do use it as a system font and may not be aware of the design resources page, I'd like to see the TTF still included in the download, even if it's not in the CSS.

@Pomax

This comment has been minimized.

Show comment
Hide comment
@Pomax

Pomax Apr 13, 2017

Note that in terms of official support, Microsoft only supports IE11 and Edge "latest", with IE9 support for Windows Vista SP2 users having ended literally 2 days ago (hurray!).

Both IE11 and Edge support WOFF, but due to EOL promises IE11 will stay supported for as long as Windows 10 is, as that's the browser that it technically came with... that said, realistically you're looking at IE11 support until windows 7 goes out of support in 2020.

Pomax commented Apr 13, 2017

Note that in terms of official support, Microsoft only supports IE11 and Edge "latest", with IE9 support for Windows Vista SP2 users having ended literally 2 days ago (hurray!).

Both IE11 and Edge support WOFF, but due to EOL promises IE11 will stay supported for as long as Windows 10 is, as that's the browser that it technically came with... that said, realistically you're looking at IE11 support until windows 7 goes out of support in 2020.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Apr 13, 2017

Owner

Thanks @Pomax, looks like that will be the plan for the next release.

Will work to update the build scripts shortly to remove these fonts (still going to include the TTF file in the build since it's useful for devs, and I don't think they are the type to go and grab the large SVG design package).

Other than this, 2.0.xx has really no large changes that should affect users that are coming from v1.9.32 or even v1.8.36. Users from v1.7.22 might have a small hickup with a few icons and all the CSS updates, but nothing that can't be solved in a few minutes.

Owner

Templarian commented Apr 13, 2017

Thanks @Pomax, looks like that will be the plan for the next release.

Will work to update the build scripts shortly to remove these fonts (still going to include the TTF file in the build since it's useful for devs, and I don't think they are the type to go and grab the large SVG design package).

Other than this, 2.0.xx has really no large changes that should affect users that are coming from v1.9.32 or even v1.8.36. Users from v1.7.22 might have a small hickup with a few icons and all the CSS updates, but nothing that can't be solved in a few minutes.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian May 24, 2017

Owner

Still working on the backlog, but there are 2000 icons in MDI currently. Still need to get more in before the next release.

Owner

Templarian commented May 24, 2017

Still working on the backlog, but there are 2000 icons in MDI currently. Still need to get more in before the next release.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Jun 13, 2017

Owner

Going to be wrapping up several icons this week/weekend and doing a release. Probably going to rollover a lot of these to a new issue when that happens. It will be roughly ~2.0.20 version.

Just need to drop support for the legacy browsers.

Owner

Templarian commented Jun 13, 2017

Going to be wrapping up several icons this week/weekend and doing a release. Probably going to rollover a lot of these to a new issue when that happens. It will be roughly ~2.0.20 version.

Just need to drop support for the legacy browsers.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Jul 6, 2017

Owner

The icon count we're at right now is the release for v2.0.46, fixing a few issues due to the server migration in the webfont build process. 😄

Owner

Templarian commented Jul 6, 2017

The icon count we're at right now is the release for v2.0.46, fixing a few issues due to the server migration in the webfont build process. 😄

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Jul 18, 2017

Owner

https://materialdesignicons.com/cdn/2.0.46/

Doing some testing and will update the bower/npm shortly.

Owner

Templarian commented Jul 18, 2017

https://materialdesignicons.com/cdn/2.0.46/

Doing some testing and will update the bower/npm shortly.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Jul 21, 2017

Owner

NPM/Bower release is out for SVG 2.0.46: https://github.com/templarian/materialdesign-svg

Ran into a minor regression bug that prevented me from releasing yesterday. Will be releasing tomorrow, then back to adding tons of icons. 😓 😄

Owner

Templarian commented Jul 21, 2017

NPM/Bower release is out for SVG 2.0.46: https://github.com/templarian/materialdesign-svg

Ran into a minor regression bug that prevented me from releasing yesterday. Will be releasing tomorrow, then back to adding tons of icons. 😓 😄

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Jul 24, 2017

Owner

By the way npm/bower were updated to 2.0.46.

Now we play the waiting game to see if anything broke. Building more rigorous automated testing, but might need to start putting in code review checks with others before releases.

https://cdn.materialdesignicons.com/2.0.46/
The svg directory will also be the repo for those needing the meta.json outside of the CDN.

Will update the website tomorrow with the new version numbers.

Owner

Templarian commented Jul 24, 2017

By the way npm/bower were updated to 2.0.46.

Now we play the waiting game to see if anything broke. Building more rigorous automated testing, but might need to start putting in code review checks with others before releases.

https://cdn.materialdesignicons.com/2.0.46/
The svg directory will also be the repo for those needing the meta.json outside of the CDN.

Will update the website tomorrow with the new version numbers.

@Templarian

This comment has been minimized.

Show comment
Hide comment
@Templarian

Templarian Jul 25, 2017

Owner

Closing moving discussion over to #2280

Owner

Templarian commented Jul 25, 2017

Closing moving discussion over to #2280

@Templarian Templarian closed this Jul 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment