hello folks... ftr: master is currently looking pretty green internally at twitter, so i've created a 1.15.x milestone (https://github.com/pantsbuild/pants/milestone/23) to account for things that might block cutting the branch, or be cherry-picked

Are we still doing a dev release this Friday so that we can release Py3? That seems like a dev release and not RC thing since it’s experimental

well, i think the question of dev vs rc is one of: "what would we want to learn from the dev release before deciding that we can cut"

I think we’d want to confirm Py3 can be consumed externally without hiccups, which with anything new we should expect hiccups. RC is fine with me if you think it’s appropriate though! Important thing to me is the feature ships

if there are questions that need to be answered before you're comfortable cutting an rc (ie, before we begin to cherry-pick fixes rather than just landing them in master), then you might want to pose those as part of a dev release

Yes, all the above do block—I left off the one unrelated refactor I did

k

I like this idea. If we don’t land the doc changes and setup changes before release, then we can give ourselves the weekend to validate everything and send a dedicated email about Python 3 support near the beginning of the week

would decouple your initial testing from the releaser releasing