Whoa, cool subthread-forking feature, very nice.
Some I things I like very much about the SPP proposal:
- Provides an easy path for publishing. Everyone wrestles with this — it would be great to have something both standard and simple. (Jorge, you might look at the Travis-based push-tag-to-publish-stuff we already have for Scala modules like scala-xml and scala-parser-combinators. Your thing may already be better, I don’t know.)
- Provides nightly builds — most projects don’t even bother wrestling with this because it’s a pain. Getting this for free would be awesome.
- Great committee — good recruiting there.
Some questions:
- Is the sbt-platform plugin actually required to be part of the platform, or is it just an optional thing that projects can decide if they like? If it is required, might there be any reasons that members might hesitate to adopt it? Any compatibility concerns? Also, sometimes projects already have a lot of this type of infrastructure in place, and even if a superior alternative is offered, replacing the old stuff is work. (Maybe the concept of platform-release branch means member projects would have the option of leaving their main branches alone?)
- Travis works fine for me, it’s free, and I already know how to use it. What’s the benefit of switching to Drone?