Skip to content

Update to support 26, gradle 4.1. Changes min to 14 #716

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 2 commits into from
Aug 23, 2017
Merged

Update to support 26, gradle 4.1. Changes min to 14 #716

merged 2 commits into from
Aug 23, 2017

Conversation

Jawnnypoo
Copy link
Member

This should probably be a bump to 1.16.0, since the min version will be bumped from 9 to 14

@codecov
Copy link

codecov bot commented Aug 22, 2017

Codecov Report

Merging #716 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##             master    #716   +/-   ##
========================================
  Coverage        53%     53%           
  Complexity     1732    1732           
========================================
  Files           132     132           
  Lines         10266   10266           
  Branches       1434    1434           
========================================
  Hits           5441    5441           
  Misses         4376    4376           
  Partials        449     449

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 78ca0f2...82dca35. Read the comment docs.

@natario1
Copy link
Contributor

Is this reasonably safe? I mean, no one using 9-13 anymore?

@iernie
Copy link
Contributor

iernie commented Aug 23, 2017

According to https://developer.android.com/about/dashboards/index.html#Platform API <10 && 11-14 has a usage of less than 0.1% while API 10 has a usage of 0.7%.

If Google deprecated API <14 in their support library I think it's safe to do the same. At some point you have to stop supporting outdated software.

@natario1
Copy link
Contributor

I think the same, other popular SDKs do the same, for instance Facebook SDK stands at 15. I was asking because right now this is not strictly needed, we are only using annotations that would still be working fine AFAIK.

On the other hand, the no-dependencies, support-everyone policy has probably done some harm to this repo in the past (thinking about the current push status). So yeah, fine for me.

We should update Parse-UI and other stuff as well

@Jawnnypoo Jawnnypoo merged commit e0391f7 into parse-community:master Aug 23, 2017
@Jawnnypoo Jawnnypoo deleted the updates branch August 23, 2017 14:04
@mchun
Copy link

mchun commented Nov 4, 2017

This is how planned obsolescence works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants