pantsbuild #announce

@rough-minister-58256: i believe that more frequent external stable releases might be a way to avoid needing a separate internal cherry-pick process.

witty-crayon-22786

01/10/2018, 1:25 AM

maybe monthly.

witty-crayon-22786

01/10/2018, 1:26 AM

@enough-analyst-54434: this "cherry-pick things from master onto a branch off master" is exactly the same as the stable release process in the pantsbuild.org docs

witty-crayon-22786

01/10/2018, 1:27 AM

so the

1.3.x

branch contains some old master sha, and then a series of cherry-picked prs from master (and hopefully nothing else)

witty-crayon-22786

01/10/2018, 1:27 AM

our internal releases are the same

rough-minister-58256

01/10/2018, 1:28 AM

are you hoping to cut 1.4.0 e.g. today and supplant the current release w/ that as stable?

witty-crayon-22786

01/10/2018, 1:28 AM

yes.

rough-minister-58256

01/10/2018, 1:28 AM

and then keep that up going forward?

witty-crayon-22786

01/10/2018, 1:28 AM

yes.

rough-minister-58256

01/10/2018, 1:28 AM

witty-crayon-22786

01/10/2018, 1:29 AM

the result would be much more frequent stable releases.

witty-crayon-22786

01/10/2018, 1:29 AM

(approximately monthly, as that seems to be about how long it takes us to stabilize one of these)

rough-minister-58256

01/10/2018, 1:29 AM

would that mean our internal releaser would need to coordinate w/ the broader community to cut a few rcs, get feedback, cp, etc then cut a stable - then we consume that directly?

rough-minister-58256

01/10/2018, 1:29 AM

seems like it could potentially complicate an already complicated release process.

enough-analyst-54434

01/10/2018, 1:30 AM

Once the stable release is monthly I'd venture that moving to just using weekly would be a small step. The delta in changes between 4 weeks and 1 is small (1/4!)

witty-crayon-22786

01/10/2018, 1:30 AM

i think that the potential advantage is that it not longer feels dirty to use community resources to validate a stable branch.

rough-minister-58256

01/10/2018, 1:30 AM

I’d be on board, but probably deserves a broader chat w/ the team since we’d all be signing up for that

witty-crayon-22786

01/10/2018, 1:30 AM

@enough-analyst-54434: how do you cherry pick in that case?

witty-crayon-22786

01/10/2018, 1:31 AM

i really, really don't see a situation in which we do not cherry-pick.

enough-analyst-54434

01/10/2018, 1:31 AM

As the time delta goes to 0 so do cherry picks

enough-analyst-54434

01/10/2018, 1:31 AM

there stablity edits to mainline

enough-analyst-54434

01/10/2018, 1:31 AM

And I'm pointing out 1 month gets things mighty close to that

witty-crayon-22786

01/10/2018, 1:32 AM

but how would you actually consume a release if you needed to wait a week between attempts?

rough-minister-58256

01/10/2018, 1:32 AM

this would all be much more appealing if folks outside of Twitter were also on board with this plan and willing to chair some share of releases

witty-crayon-22786

01/10/2018, 1:33 AM

basically, it might work if you could stop time and/or block commits to master long enough to test and fix all issues and then land the release

enough-analyst-54434

01/10/2018, 1:34 AM

I'd just love for Twitter to get on board with (I think it is) using stable releases and contributing to them. The move towards 1 month stables would do that

witty-crayon-22786

01/10/2018, 1:34 AM

ok, then i think we're in agreement.