So the mythical Apple car project actually goes way back :)
Release branches are fine (mobile apps, sure... web apps, probably not). Again, context is key. You can still integrate to trunk as one would expect in TBD, no need for the delayed integration in Gitflow. A common…
It's rather funny. "Trunk-based development" is essentially counter-marketing to Gitflow. Before Gitflow, trunk-based development was so routine it didn't need a proper name or website. Gitflow has the "interesting"…
>How will they do that exactly? Presumably they could have the dx tool in the current toolchain support Java 8 bytecode .class files as input (just as the Jill linker in Jack toolchain allows). >I thought the whole…
>The possibility of running Scala >=2.12 (or any other language that is committed to Java 8[1]) on Android seems even more remote now To quote the article: "We've decided to add support for Java 8 language features…
So the mythical Apple car project actually goes way back :)
Release branches are fine (mobile apps, sure... web apps, probably not). Again, context is key. You can still integrate to trunk as one would expect in TBD, no need for the delayed integration in Gitflow. A common…
It's rather funny. "Trunk-based development" is essentially counter-marketing to Gitflow. Before Gitflow, trunk-based development was so routine it didn't need a proper name or website. Gitflow has the "interesting"…
>How will they do that exactly? Presumably they could have the dx tool in the current toolchain support Java 8 bytecode .class files as input (just as the Jill linker in Jack toolchain allows). >I thought the whole…
>The possibility of running Scala >=2.12 (or any other language that is committed to Java 8[1]) on Android seems even more remote now To quote the article: "We've decided to add support for Java 8 language features…