| ▲ | charcircuit a day ago |
| >ensure platform stability for the ecosystem Aka "We will do less releases because certain OEMs don't want to be seen as outdated as they don't want to spend the resources to rebase even 4 times per year." |
|
| ▲ | dvdkon a day ago | parent | next [-] |
| That's not clear to me: Will they do fewer releases, or will they have the same quarterly release cadence as now, just with only every second release open source? |
| |
| ▲ | charcircuit a day ago | parent [-] | | I would assume the Q1 and Q3 quarterly releases are going away altogether. | | |
|
|
| ▲ | fluidcruft a day ago | parent | prev [-] |
| Well it does prevent them from shipping things prematurely. I guess. |
| |
| ▲ | charcircuit a day ago | parent [-] | | They can still ship play services and their own apps at a faster cadence. | | |
| ▲ | fluidcruft a day ago | parent [-] | | I meant OEMs rushing the gun on new features that aren't fully baked. That probably does add support burden. (I don't know if it happens anymore but it used to be a problem on the OEM forks) | | |
| ▲ | Groxx a day ago | parent [-] | | They push half-baked stuff all the time anyway, I don't think this meaningfully affects that frequency. | | |
| ▲ | gitttnwmrlg a day ago | parent [-] | | Well, now they can only ship half baked stuff twice a year. | | |
| ▲ | a day ago | parent | next [-] | | [deleted] | |
| ▲ | charcircuit a day ago | parent | prev [-] | | They should at least be shipping monthly updates with the months security updates. Well some months have not had any since Google is now trying to batch them to be quarterly because OEMs couldn't keep up with monthly security fixes. |
|
|
|
|
|
