forked from pantsbuild/pantsbuild.github.io
/
release.html
570 lines (547 loc) · 25.1 KB
/
release.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
<!DOCTYPE html>
<html lang="en">
<!--
Copyright 2014 Pants project contributors (see CONTRIBUTORS.md).
Licensed under the Apache License, Version 2.0 (see LICENSE).
-->
<head>
<meta charset="utf-8"/>
<title>Release Process</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="shortcut icon" href="pants-logo.ico">
<!-- In case this is a "test publish", tell search engines where real version lives: -->
<link rel="canonical" href="http://pantsbuild.org/release.html">
<link rel="stylesheet" href="bootstrap-custom.min.css">
<link rel="stylesheet" href="bootstrap-custom-theme.min.css">
<link rel="stylesheet" href="docsite.css">
</head>
<body>
<div class="header">
<nav class="navbar navbar-default navbar-static-top">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand navbar-brand-img" href="index.html">
<img src="pants-logo.ico" alt="[pantsbuild logo]">
</a>
<a class="navbar-brand" href="index.html">
Pants
</a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav navbar-right">
<li><a href="/">Docs</a></li>
<li><a href="community.html">Community</a></li>
<li><a href="https://www.github.com/pantsbuild/pants">GitHub</a></li>
<li>
<form class="navbar-form navbar-left search" role="search" action="https://www.google.com/search">
<div class="form-group">
<input type="text" name="as_q" class="form-control query" placeholder="Search">
<input name="as_sitesearch" value="pantsbuild.org" type="hidden">
</div>
</form>
</li>
</ul>
</div><!--/.nav-collapse -->
</div>
</nav>
</div>
<div class="page">
<div class="container-fluid">
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-2">
<div class="site-toc">
<ul>
<li class="toc-h1 toc-heading">
Getting Started
</li>
<li class="toc-h1 toc-link ">
<a href="install.html">Installing Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="setup_repo.html">Setting Up Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="first_tutorial.html">Tutorial</a>
</li>
<li class="toc-h1 toc-link ">
<a href="common_tasks.html">Common Tasks</a>
</li>
<li class="toc-h1 toc-heading">
Pants Basics
</li>
<li class="toc-h1 toc-link ">
<a href="why_use_pants.html">Why Use Pants?</a>
</li>
<li class="toc-h1 toc-link ">
<a href="first_concepts.html">Pants Concepts</a>
</li>
<li class="toc-h1 toc-link ">
<a href="build_files.html">BUILD files</a>
</li>
<li class="toc-h1 toc-link ">
<a href="target_addresses.html">Target Addresses</a>
</li>
<li class="toc-h1 toc-link ">
<a href="3rdparty.html">Third-Party Dependencies</a>
</li>
<li class="toc-h1 toc-link ">
<a href="options.html">Pants Options</a>
</li>
<li class="toc-h1 toc-link ">
<a href="invoking.html">Invoking Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="reporting_server.html">Reporting Server</a>
</li>
<li class="toc-h1 toc-link ">
<a href="ide_support.html">IDE Support</a>
</li>
<li class="toc-h1 toc-heading">
JVM
</li>
<li class="toc-h1 toc-link ">
<a href="jvm_projects.html">JVM Projects with Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="3rdparty_jvm.html">JVM 3rdparty Pattern</a>
</li>
<li class="toc-h1 toc-link ">
<a href="scala.html">Scala Support</a>
</li>
<li class="toc-h1 toc-link ">
<a href="publish.html">Publishing Artifacts</a>
</li>
<li class="toc-h1 toc-link ">
<a href="from_maven.html">Pants for Maven Experts</a>
</li>
<li class="toc-h1 toc-heading">
Python
</li>
<li class="toc-h1 toc-link ">
<a href="python_readme.html">Python Projects with Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="3rdparty_py.html">Python 3rdparty Pattern</a>
</li>
<li class="toc-h1 toc-heading">
Go
</li>
<li class="toc-h1 toc-link ">
<a href="go_readme.html">Go support for Pants</a>
</li>
<li class="toc-h1 toc-heading">
Codegen
</li>
<li class="toc-h1 toc-link ">
<a href="thrift_deps.html">Thrift</a>
</li>
<li class="toc-h1 toc-heading">
Docgen
</li>
<li class="toc-h1 toc-link ">
<a href="page.html">Markdown</a>
</li>
<li class="toc-h1 toc-heading">
Getting Help
</li>
<li class="toc-h1 toc-link ">
<a href="tshoot.html">Troubleshooting</a>
</li>
<li class="toc-h1 toc-link ">
<a href="community.html">Community</a>
</li>
<li class="toc-h1 toc-heading">
Reference
</li>
<li class="toc-h1 toc-link ">
<a href="build_dictionary.html">Pants BUILD Dictionary</a>
</li>
<li class="toc-h1 toc-link ">
<a href="options_reference.html">Pants Reference</a>
</li>
<li class="toc-h1 toc-heading">
Release Notes
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.3.x.html">1.3.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.2.x.html">1.2.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.1.x.html">1.1.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.0.x.html">1.0.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-master.html">Master Pre-Releases</a>
</li>
<li class="toc-h1 toc-heading">
Developer
</li>
<li class="toc-h1 toc-link ">
<a href="dev.html">Pants Developer Center</a>
</li>
<li class="toc-h1 toc-link ">
<a href="export.html">Export Format</a>
</li>
</ul>
</div> <!-- site-toc -->
</div>
<div class="col-md-8">
<div class="content">
<div class="mainflow">
<nav class="pagetoc">
<ul>
<li class="toc-h1"><a href="#prerequisites">Prerequisites</a></li>
<li class="toc-h1"><a href="#prepare-release">Prepare Release</a></li>
<li class="toc-h1"><a href="#releasing-from-different-release-branches">Releasing from different release branches</a></li>
<li class="toc-h2"><a href="#preparation-for-the-release-from-the-master-branch">Preparation for the release from the master branch</a></li>
<li class="toc-h2"><a href="#preparation-for-the-release-from-the-stable-branch">Preparation for the release from the stable branch</a></li>
<li class="toc-h1"><a href="#dry-run-optional">Dry Run (Optional)</a></li>
<li class="toc-h1"><a href="#publish-to-pypi">Publish to PyPi</a></li>
<li class="toc-h1"><a href="#announce">Announce</a></li>
<li class="toc-h1"><a href="#owners">Owners</a></li>
</ul>
</nav>
<!-- main content start -->
<!-- generated by pants! -->
<style>
.codehilite .hll { background-color: #ffffcc }
.codehilite { background: #f0f0f0; }
.codehilite .c { color: #60a0b0; font-style: italic } /* Comment */
.codehilite .err { border: 1px solid #FF0000 } /* Error */
.codehilite .k { color: #007020; font-weight: bold } /* Keyword */
.codehilite .o { color: #666666 } /* Operator */
.codehilite .cm { color: #60a0b0; font-style: italic } /* Comment.Multiline */
.codehilite .cp { color: #007020 } /* Comment.Preproc */
.codehilite .c1 { color: #60a0b0; font-style: italic } /* Comment.Single */
.codehilite .cs { color: #60a0b0; background-color: #fff0f0 } /* Comment.Special */
.codehilite .gd { color: #A00000 } /* Generic.Deleted */
.codehilite .ge { font-style: italic } /* Generic.Emph */
.codehilite .gr { color: #FF0000 } /* Generic.Error */
.codehilite .gh { color: #000080; font-weight: bold } /* Generic.Heading */
.codehilite .gi { color: #00A000 } /* Generic.Inserted */
.codehilite .go { color: #808080 } /* Generic.Output */
.codehilite .gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */
.codehilite .gs { font-weight: bold } /* Generic.Strong */
.codehilite .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
.codehilite .gt { color: #0040D0 } /* Generic.Traceback */
.codehilite .kc { color: #007020; font-weight: bold } /* Keyword.Constant */
.codehilite .kd { color: #007020; font-weight: bold } /* Keyword.Declaration */
.codehilite .kn { color: #007020; font-weight: bold } /* Keyword.Namespace */
.codehilite .kp { color: #007020 } /* Keyword.Pseudo */
.codehilite .kr { color: #007020; font-weight: bold } /* Keyword.Reserved */
.codehilite .kt { color: #902000 } /* Keyword.Type */
.codehilite .m { color: #40a070 } /* Literal.Number */
.codehilite .s { color: #4070a0 } /* Literal.String */
.codehilite .na { color: #4070a0 } /* Name.Attribute */
.codehilite .nb { color: #007020 } /* Name.Builtin */
.codehilite .nc { color: #0e84b5; font-weight: bold } /* Name.Class */
.codehilite .no { color: #60add5 } /* Name.Constant */
.codehilite .nd { color: #555555; font-weight: bold } /* Name.Decorator */
.codehilite .ni { color: #d55537; font-weight: bold } /* Name.Entity */
.codehilite .ne { color: #007020 } /* Name.Exception */
.codehilite .nf { color: #06287e } /* Name.Function */
.codehilite .nl { color: #002070; font-weight: bold } /* Name.Label */
.codehilite .nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */
.codehilite .nt { color: #062873; font-weight: bold } /* Name.Tag */
.codehilite .nv { color: #bb60d5 } /* Name.Variable */
.codehilite .ow { color: #007020; font-weight: bold } /* Operator.Word */
.codehilite .w { color: #bbbbbb } /* Text.Whitespace */
.codehilite .mf { color: #40a070 } /* Literal.Number.Float */
.codehilite .mh { color: #40a070 } /* Literal.Number.Hex */
.codehilite .mi { color: #40a070 } /* Literal.Number.Integer */
.codehilite .mo { color: #40a070 } /* Literal.Number.Oct */
.codehilite .sb { color: #4070a0 } /* Literal.String.Backtick */
.codehilite .sc { color: #4070a0 } /* Literal.String.Char */
.codehilite .sd { color: #4070a0; font-style: italic } /* Literal.String.Doc */
.codehilite .s2 { color: #4070a0 } /* Literal.String.Double */
.codehilite .se { color: #4070a0; font-weight: bold } /* Literal.String.Escape */
.codehilite .sh { color: #4070a0 } /* Literal.String.Heredoc */
.codehilite .si { color: #70a0d0; font-style: italic } /* Literal.String.Interpol */
.codehilite .sx { color: #c65d09 } /* Literal.String.Other */
.codehilite .sr { color: #235388 } /* Literal.String.Regex */
.codehilite .s1 { color: #4070a0 } /* Literal.String.Single */
.codehilite .ss { color: #517918 } /* Literal.String.Symbol */
.codehilite .bp { color: #007020 } /* Name.Builtin.Pseudo */
.codehilite .vc { color: #bb60d5 } /* Name.Variable.Class */
.codehilite .vg { color: #bb60d5 } /* Name.Variable.Global */
.codehilite .vi { color: #bb60d5 } /* Name.Variable.Instance */
.codehilite .il { color: #40a070 } /* Literal.Number.Integer.Long */
</style>
<h1 id="release-process">Release Process</h1>
<p>This page describes how to make a versioned release of Pants and and
other related packages to PyPi. If you need to release pants jvm tools
(jars), see the
<a href="release_jvm.html">JVM Artifact Release Process</a>
page.</p>
<p>Deciding the "who", "what", and "when" of releasing is described on the
<a href="release_strategy.html">Release Strategy</a> page. Note that for some
lucky release managers, this may result in two or more releases in a particular week.</p>
<p>Once you know what to release, releasing pants involves:</p>
<ul>
<li>Preparing the release.</li>
<li>(optional) Perform a release dry run.</li>
<li>Publishing the release to PyPi.</li>
<li>Announce the release on pants-devel.</li>
</ul>
<h2 id="prerequisites">Prerequisites</h2>
<p>There are several things that require one-time setup in order to be
able to perform pants releases. The release script checks that all
these steps have been performed in one way or another, but you might
like to go through this list ahead of time rather than have the release
script fail:</p>
<ul>
<li>
<p>Create a pgp signing key if you don't already have one.</p>
<p>You might use the gpg implemntation of pgp and start here:
https://www.gnupg.org/gph/en/manual/c14.html</p>
</li>
<li>
<p>If using gpg, ensure that the gpg-agent is running (for OS X, see
instructions <a href="https://blog.chendry.org/2015/03/13/starting-gpg-agent-in-osx.html">here</a>),
and ensure that gpg is set up to use it (e.g., set <code>use-agent</code> in <code>~/.gnupg/gpg.conf</code>).</p>
</li>
<li>
<p>Configure git to use your pgp key for signing release tags.</p>
<p>A description of the configuration can be found here:
https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work#GPG-Introduction</p>
</li>
<li>
<p>Create a pypi account if you don't already have one.</p>
<p>You can register here: https://pypi.python.org/pypi?%3Aaction=register_form
Don't forget to include your pgp key id even though pypi considers
this step optional.</p>
</li>
<li>
<p>Get your pypi account added as an <code>owner</code> for all pantsbuild.pants packages.</p>
<p>You can ask any one of the <a href="#owners">Owners</a> listed below to do this.
Once this is done and you've performed your 1st release, add yourself to
the <a href="#owners">Owners</a> section below.</p>
</li>
<li>
<p>Configure your pypi credentials locally in <code>~/.pypirc</code></p>
<p>For some versions of python it's necessary to use both a <code>server-login</code> and
<code>pypi</code> section containing the same info. This will do it:</p>
<div class="codehilite"><pre>cat <span class="s"><< EOF > ~/.pypirc && chmod 600 ~/.pypirc</span>
<span class="s">[pypi]</span>
<span class="s">username: <fill me in></span>
<span class="s">password: <fill me in></span>
<span class="s">[server-login]</span>
<span class="s">username: <fill me in></span>
<span class="s">password: <fill me in></span>
<span class="s">EOF</span>
</pre></div>
</li>
<li>
<p>Note that the release script expects your pantsbuild/pants git remote to be named <code>origin</code>.
If you have another name for it, you should <code>git remote rename othername origin</code> before running
the release script, and rename it back afterwards.</p>
</li>
</ul>
<h2 id="prepare-release">Prepare Release</h2>
<p>Pants and the common libraries are published to the <a href="https://pypi.python.org/pypi">Python Package
Index</a> per the Python community
convention.</p>
<p>Although the build and publish are automated, the version bumping, changelog edits,
and CONTRIBUTORS management are not. Changelog edits and CONTRIBUTOR updates always
occur in master, while version changes generally only occur in the relevant release branch.</p>
<h2 id="releasing-from-different-release-branches">Releasing from different release branches</h2>
<p>Every week we do a release from master. In most cases we will use the <code>dev</code> naming convention
detailed in <a href="http://www.pantsbuild.org/release_strategy.html">Release Strategy</a>. When we are
ready to create a new stable branch we will release under the <code>rc</code> naming convention instead of
<code>dev</code>. For example releases in master should look similar to the following: 1.1.0dev0, 1.1.0dev1,
1.1.0dev2, 1.1.0rc0, 1.2.0dev0, 1.2.0dev1, 1.2.0rc0, 1.3.0dev0. <em>In addition to a release from master
the release manager may also need to do a release from a stable branch.</em></p>
<ul>
<li>
<h3 id="preparation-for-the-release-from-the-master-branch">Preparation for the release from the master branch</h3>
<ol>
<li>Edit the version number in <code>src/python/pants/version.py</code></li>
<li>Update <code>src/python/pants/notes/master.rst</code> to reflect the changes for this week (can use
<code>build-support/bin/release-changelog-helper.sh</code> to get a head start).</li>
<li>If this release is also a release candidate then:<ul>
<li>Create the corresponding notes file for that release, initialized with notes for all
<code>dev</code> releases in the series. <br/>
<em>For example if you were releasing <code>1.2.0rc0</code> you would need to
create <code>src/python/pants/notes/1.2.x.rst</code> and include all <code>1.2.0devX</code> release notes.</em></li>
<li>Add the file to pants.ini in the branch_notes section.</li>
<li>Add the new notes file to <code>src/docs/docsite.json</code>.</li>
<li>Create a new page() in <code>src/python/pants/notes/BUILD</code> corresponding to the new notes. <br/>
For additional information on generating documentation see the
<a href="http://www.pantsbuild.org/docs#generating-the-site">docs reference</a></li>
</ul>
</li>
<li>Bring the CONTRIBUTORS roster (from master) in
<a href="https://github.com/pantsbuild/pants/tree/master/CONTRIBUTORS.md">CONTRIBUTORS.md</a>
up to date by running <code>build-support/bin/contributors.sh</code>.</li>
<li>Create and land a review for changes in the master branch.</li>
<li>Execute the release as described later on this page.</li>
<li>Finally, if creating a release candidate, create the stable branch from the commit in
master for your release. For example if you were releasing <code>1.2.0rc0</code>, create the branch
<code>1.2.x</code> from your release commit.</li>
</ol>
</li>
<li>
<h3 id="preparation-for-the-release-from-the-stable-branch">Preparation for the release from the stable branch</h3>
<p>See <a href="http://www.pantsbuild.org/release_strategy.html">Release Strategy</a> for more details about
whether a release is needed from a stable branch.</p>
<ol>
<li>Cherry pick <a href="https://github.com/pantsbuild/pants/pulls?q=is%3Apr+label%3Aneeds-rc-cherrypick">changes labelled needs-rc-cherrypick</a>
directly to the stable branch. Note that these pull requests must have been merged into master, and
therefore will be closed.</li>
<li>In master, update <code>src/python/pants/notes/*.rst</code> to reflect all patches that were
cherry-picked (can use <code>build-support/bin/release-changelog-helper.sh</code> to get a head start).
For example if you were releasing 1.2.0rc1 you would edit <code>src/python/pants/notes/1.2.x.rst</code>.</li>
<li>Create and land a review for the notes changes in master.</li>
<li>Cherry pick the merged notes changes from master to the release branch.</li>
<li>In your release branch: edit and commit the version number in <code>src/python/pants/version.py</code>.</li>
<li>Execute the release as described later on this page.</li>
<li>Remove the <code>needs-rc-cherrypick</code> label from the changes cherry-picked into the new release.</li>
</ol>
</li>
</ul>
<h2 id="dry-run-optional">Dry Run (Optional)</h2>
<p>A dry run is not strictly required since CI includes one, but you might
like to try one anyway; if so, releases should only be published from
master, so get on master and ensure your version number commit is present.
After confirming this, run.</p>
<div class="codehilite"><pre><span class="nv">$ </span>./build-support/bin/release.sh -n
</pre></div>
<p>This will perform a dry run local build of the pantsbuild.pants sdist
and other related package sdists, install them in a virtualenv and then
smoke test basic operations.</p>
<p>Note that in addition to CI checking dry runs work, the release publish
flow also performs a mandatory dry run so executing a dry run separately
is not required.</p>
<h2 id="publish-to-pypi">Publish to PyPi</h2>
<p>Now that we've smoke-tested this release, we can publish to PyPi:</p>
<div class="codehilite"><pre><span class="nv">$ </span>./build-support/bin/release.sh
</pre></div>
<p>This also performs a dry run and then proceeds to upload the smoke
tested sdists to PyPi.</p>
<h2 id="announce">Announce</h2>
<p>Check PyPi to ensure everything looks good. The <a href="https://pypi.python.org/pypi/pantsbuild.pants">pantsbuild.pants
package index page</a>
should display the package version you just uploaded. The same check
applies to other related package PyPi pages.</p>
<p>To test the packages are installable:</p>
<div class="codehilite"><pre><span class="nv">$ </span>./build-support/bin/release.sh -t
</pre></div>
<p>This will attempt to install the just-published packages from pypi and
then smoke test them.</p>
<p>Finally, announce the release to pants-devel. You can get a
contributor list for the email by running the following where <code><tag></code>
if the tag for the prior release (eg: release_0.0.33)</p>
<div class="codehilite"><pre><span class="nv">$ </span>./build-support/bin/contributors.sh -s <tag>
</pre></div>
<h2 id="owners">Owners</h2>
<p>The following folks are set up to publish to pypi for
pantsbuild.pants sdists:</p>
<table>
<thead>
<tr>
<th>Name</th>
<th>Email</th>
<th>PYPI Usename</th>
</tr>
</thead>
<tbody>
<tr>
<td>John Sirois</td>
<td>john.sirois@gmail.com</td>
<td>john.sirois</td>
</tr>
<tr>
<td>Benjy Weinberger</td>
<td>benjyw@gmail.com</td>
<td>benjyw</td>
</tr>
<tr>
<td>Eric Ayers</td>
<td>ericzundel@squareup.com</td>
<td>ericzundel</td>
</tr>
<tr>
<td>Ity Kaul</td>
<td>itykaul@gmail.com</td>
<td>ity</td>
</tr>
<tr>
<td>Stu Hood</td>
<td>stuhood@gmail.com</td>
<td>stuhood</td>
</tr>
<tr>
<td>Patrick Lawson</td>
<td>patrick.a.lawson@gmail.com</td>
<td>Patrick.Lawson</td>
</tr>
<tr>
<td>Garrett Malmquist</td>
<td>garrett.malmquist@gmail.com</td>
<td>gmalmquist</td>
</tr>
<tr>
<td>Matt Olsen</td>
<td>digwanderlust@gmail.com</td>
<td>digiwanderlust</td>
</tr>
<tr>
<td>Mateo Rodriguez</td>
<td>mateorod9@gmail.com</td>
<td>mateor</td>
</tr>
</tbody>
</table>
<p>And the current list of packages that these folks can release can
be obtained via:</p>
<div class="codehilite"><pre><span class="nv">$ </span>./build-support/bin/release.sh -l
</pre></div>
<p>Right now that's:</p>
<ul>
<li>pantsbuild.pants</li>
<li>pantsbuild.pants.contrib.android</li>
<li>pantsbuild.pants.contrib.buildgen</li>
<li>pantsbuild.pants.contrib.scrooge</li>
<li>pantsbuild.pants.testinfra</li>
</ul>
<p>You can run the following to get a full ownership roster for each
package :</p>
<div class="codehilite"><pre><span class="nv">$ </span>./build-support/bin/release.sh -o
</pre></div>
<!-- main content end -->
<div class="generated">
Generated by <a href="docs.html">publish_docs</a>
from dist/markdown/html/src/docs/release.html 2017-05-29T10:30:50.973060
</div>
</div> <!-- mainflow -->
</div> <!-- content -->
</div>
<div class="col-md-1">
</div>
</div> <!-- row -->
</div> <!-- container-fluid -->
</div> <!-- page -->
<script src="https://code.jquery.com/jquery-2.2.3.min.js" integrity="sha384-I6F5OKECLVtK/BL+8iSLDEHowSAfUo76ZL9+kGAgTRdiByINKJaqTPH/QVNS1VDb" crossorigin="anonymous"></script>
<script src="bootstrap-custom.min.js"></script>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-78111411-1', 'auto');
ga('send', 'pageview');
</script>
</body>
</html>