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

    witty-crayon-22786

    05/06/2017, 3:10 AM
    mm
  • r

    rough-minister-58256

    05/06/2017, 3:11 AM
    think our only option is to fix fwd if it breaks
  • r

    rough-minister-58256

    05/06/2017, 3:11 AM
    afaict
  • r

    rough-minister-58256

    05/06/2017, 3:11 AM
    oh wait, can we just push a random tag
  • w

    witty-crayon-22786

    05/06/2017, 3:11 AM
    yea, fine with me.
  • w

    witty-crayon-22786

    05/06/2017, 3:11 AM
    er, either thing. but yea, the tag should be really easy
  • w

    witty-crayon-22786

    05/06/2017, 3:12 AM
    and can delete it later too.
  • r

    rough-minister-58256

    05/06/2017, 3:12 AM
    rgr
  • w

    witty-crayon-22786

    05/06/2017, 3:50 AM
    will be cutting 
    1.3.0.rc0
    on sunday most likely
  • r

    rough-minister-58256

    05/06/2017, 4:17 AM
  • w

    witty-crayon-22786

    05/08/2017, 4:55 PM
    anyone else interested in putting an eyeball on https://github.com/pantsbuild/pants/pull/4562 ?
  • w

    witty-crayon-22786

    05/08/2017, 5:04 PM
    <!here|@here> : sorry for the ping... would appreciate a non-twitter review on this one
    đź‘€ 1
  • w

    witty-crayon-22786

    05/08/2017, 5:06 PM
    thanks!
  • w

    witty-crayon-22786

    05/08/2017, 5:18 PM
    @brash-oxygen-26029 : responded, thanks!
  • w

    witty-crayon-22786

    05/10/2017, 3:47 PM
    https://github.com/pantsbuild/pants/pull/4561 adds a new public API that we're hoping will get a lot of use. a non-twitter review would be nice
  • w

    witty-crayon-22786

    05/10/2017, 7:30 PM
    thanks Benjy!
  • h

    happy-kitchen-89482

    05/10/2017, 8:45 PM
    Do we have a way for the author of a change to mark it as “I recommend this be cherrypicked into the next rc release”, when we’re in an rc cycle?
  • h

    happy-kitchen-89482

    05/10/2017, 8:46 PM
    Currently it’s at the releaser’s discretion, I think.
  • r

    rough-minister-58256

    05/10/2017, 8:49 PM
    would probably be simplest to keep an open ticket w/ a 
    release
    label to track items that should be going in?
  • r

    rough-minister-58256

    05/10/2017, 8:59 PM
    this is how I’ve been managing all pex releases. e.g. https://github.com/pantsbuild/pex/issues/385
  • r

    rough-minister-58256

    05/10/2017, 8:59 PM
    its nice to be able to mention an issue in the description and have it linked via githubs mentions in the PR itself so there’s always a context back to the release it’s going out in.
  • r

    rough-minister-58256

    05/10/2017, 9:01 PM
    and release tickets are a great way for folks to raise and link release-related issues or ask questions without adhoc slack comms
  • w

    witty-crayon-22786

    05/10/2017, 10:52 PM
    @happy-kitchen-89482 i've been targetting things at the 1.3.0 milestone
  • w

    witty-crayon-22786

    05/10/2017, 10:53 PM
    but that's isn't really codified yet. technically we still mention the "Backports Spreadsheet", but i think milestones are proving to be useful.
  • h

    happy-kitchen-89482

    05/10/2017, 10:54 PM
    Yeah, will just do that on the pull requests
  • h

    happy-kitchen-89482

    05/10/2017, 10:54 PM
    even though they are closed
  • w

    witty-crayon-22786

    05/10/2017, 10:54 PM
    yea, i'll look for them. that's the only catch.
  • h

    happy-kitchen-89482

    05/10/2017, 10:54 PM
    Hmm, maybe we shouldn’t close them
  • h

    happy-kitchen-89482

    05/10/2017, 10:55 PM
    But closing it is shorthand for “this is in master”, so hmm
  • w

    witty-crayon-22786

    05/10/2017, 10:55 PM
    they stay in the milestone
1...434445...206Latest