https://pantsbuild.org/ logo
Powered by
#announce
  • r

    rough-minister-58256

    04/28/2017, 11:29 PM
    woot
  • w

    witty-crayon-22786

    05/01/2017, 6:55 PM
  • h

    happy-kitchen-89482

    05/01/2017, 6:55 PM
    --no-test-pytest-fast
    runs each target in a separate pytest invocation
  • h

    happy-kitchen-89482

    05/01/2017, 6:56 PM
    But there’s still only one set of 3rdparty deps and one selected interpreter for all targets in-play
  • w

    witty-crayon-22786

    05/01/2017, 6:56 PM
    well, my question was whether there is anything else we want to do for 1.3.0 there
  • w

    witty-crayon-22786

    05/01/2017, 6:56 PM
    ie, before this friday
  • h

    happy-kitchen-89482

    05/01/2017, 6:57 PM
    Hmmm, I can try and squeeze it in.
  • h

    happy-kitchen-89482

    05/01/2017, 6:57 PM
    A way of specifying dynamically which target groupings you want to run interpreter selection and 3rdparty dep resolution for.
  • h

    happy-kitchen-89482

    05/01/2017, 6:58 PM
    But I wouldn’t delay 1.3.0rc0 for this
  • h

    happy-kitchen-89482

    05/01/2017, 6:58 PM
    If any shops have a major issue with this, they can fall back to the old pipeline
  • w

    witty-crayon-22786

    05/01/2017, 7:00 PM
    ok, sounds good
  • w

    witty-crayon-22786

    05/01/2017, 7:51 PM
    probably not a release blocker, but: https://github.com/pantsbuild/pants/issues/4536
  • w

    witty-crayon-22786

    05/01/2017, 8:03 PM
    i'm starting our internal 
    1.3.0
    incorporation branch, and will be opening a few tickets against 1.3.0 for it.
  • w

    witty-crayon-22786

    05/01/2017, 8:09 PM
    @wide-energy-11069 : since i'm doing our internal release, mind if i take over the release for this friday?
  • w

    wide-energy-11069

    05/01/2017, 8:20 PM
    @witty-crayon-22786 please go ahead. i can take your rotation next time, which is when?
  • w

    witty-crayon-22786

    05/01/2017, 8:22 PM
    do you think you could just take next week instead?
  • w

    witty-crayon-22786

    05/01/2017, 8:23 PM
    there is a hole in the calendar (blargh... need to get that fixed)
  • w

    wide-energy-11069

    05/01/2017, 8:23 PM
    sure np
  • w

    wide-energy-11069

    05/03/2017, 9:42 PM
    I’m the releaser this week, and will start the process Friday evening. is it going to be a rc branch or a dev release?
  • w

    witty-crayon-22786

    05/03/2017, 9:44 PM
    @wide-energy-11069 : i'll be doing this one... remember?
  • w

    wide-energy-11069

    05/03/2017, 9:45 PM
    oh ok. i’ll be next week then. thanks
  • w

    witty-crayon-22786

    05/03/2017, 9:46 PM
    thanks
  • w

    witty-crayon-22786

    05/03/2017, 9:46 PM
    (but yea: an rc0)
    👍 1
  • r

    rough-minister-58256

    05/04/2017, 9:19 PM
    doesn’t appear that the github kill-duplicate-prs feature works if the prior dupe job has already started 😞
  • w

    witty-crayon-22786

    05/05/2017, 5:41 PM
    heads up: i'm going to be waiting on the last few blockers, and then trying to cut this weekend
  • r

    rough-minister-58256

    05/06/2017, 12:41 AM
    hrm, anyone understand how the travis deploy stuff works?
  • r

    rough-minister-58256

    05/06/2017, 12:41 AM
    doesnt seem to be associated with any single shard
  • r

    rough-minister-58256

    05/06/2017, 12:48 AM
    seems it will also never fire for a PR.. hrm
  • w

    witty-crayon-22786

    05/06/2017, 3:10 AM
    @rough-minister-58256 : the deploy is configured to only go for tags currently
  • r

    rough-minister-58256

    05/06/2017, 3:10 AM
    yeah, and dropping that condition and firing a PR won’t test it either
1...424344...206Latest