<@UJT6PRXB9> As I was checking as list of commits ...
# composek
Klaas Kabini
05/23/2020, 3:30 AM@Mihai Popa As I was checking as list of commits you guys made on compose branch. I saw a commit that says updating compose to 0.1.0-dev14 but has not seen the one that says updating compose to 0.1.0-dev13. Was this done intentional jumping from 0.1.0-dev12 straight to 0.1.0-dev14?
j
John O'Reilly
05/23/2020, 8:36 AMhttps://developer.android.com/jetpack/androidx/releases/compose at least still shows dev11 as latest version
k
Klaas Kabini
05/23/2020, 8:37 AMYeah I know that dev11 is the latest version on maven. I was just being curious because I saw this commit in their dev branch.
a
Adam Powell
05/26/2020, 6:13 PMYes, it's intentional. We're verifying release branching strategies where we can cherry-pick fixes more easily, so dev13 is starting from a branch point equal to the dev12 build cut and master is jumping ahead to 14 to leave room.