...
 
Commits (2)
......@@ -493,7 +493,7 @@ GitHub page</a></p>
</div>
</div>
<div class="sect1">
<h2 id="_helpful_links_for_daily_tasks">Helpful links for daily tasks</h2>
<h2 id="_helpful_links_for_daily_go_packaging_tasks">Helpful links for daily Go packaging tasks</h2>
<div class="sectionbody">
<div class="ulist">
<ul>
......@@ -516,7 +516,7 @@ DDPO (Debian QA Page)</a></p>
</div>
<div id="footer">
<div id="footer-text">
Last updated 2018-06-15 10:39:09 MDT
Last updated 2018-06-15 10:47:42 MDT
</div>
</div>
</body>
......
......@@ -429,6 +429,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
#footer-text{color:rgba(0,0,0,.6);font-size:.9em}}
@media amzn-kf8{#header,#content,#footnotes,#footer{padding:0}}
</style>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
</head>
<body class="article">
<div id="header">
......@@ -452,8 +453,31 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
<p>This document lists changes to the pkg-go workflow which the pkg-go team has
agreed on.</p>
<p>This document lists changes to the pkg-go workflow which the pkg-go team
came to a consensus and which Michael Stapelberg summarized
in November 2017.</p>
</div>
<div class="paragraph">
<p>The discussion began with this email: [pkg-go] Minutes for the DebConf17 BoF:
<a href="https://alioth-lists.debian.net/pipermail/pkg-go-maintainers/Week-of-Mon-20170807/014361.html" class="bare">https://alioth-lists.debian.net/pipermail/pkg-go-maintainers/Week-of-Mon-20170807/014361.html</a></p>
</div>
<div class="admonitionblock important">
<table>
<tr>
<td class="icon">
<i class="fa icon-important" title="Important"></i>
</td>
<td class="content">
<div class="title">This proposal for workflow changes is still a work-in-progress.</div>
<div class="paragraph">
<p><code>dh-make-golang</code> has not yet adapted to this new proposed workflow.
For newcomers and the less experienced, myself included, it is recommended
to stick with the old workflow until all the infrastructures supporting
the migration to the new workflow are in place. — AF</p>
</div>
</td>
</tr>
</table>
</div>
</div>
</div>
......@@ -527,7 +551,7 @@ buildpackage</code>’s pristine-tar option, e.g. via <code>--git-pristine-tar</
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
Using <code>--git-upstream-tree=TAG</code> (the default) is not sufficient to obtain
......@@ -541,7 +565,7 @@ pkg-go’s git repositories would match the orig .tar.gz in the archive.
<table>
<tr>
<td class="icon">
<div class="title">Tip</div>
<i class="fa icon-tip" title="Tip"></i>
</td>
<td class="content">
<div class="paragraph">
......@@ -623,7 +647,7 @@ whenever new values are added or old values are removed.</p>
<table>
<tr>
<td class="icon">
<div class="title">Tip</div>
<i class="fa icon-tip" title="Tip"></i>
</td>
<td class="content">
<div class="paragraph">
......@@ -761,7 +785,7 @@ suite name <code>UNRELEASED</code>.</p>
</div>
<div id="footer">
<div id="footer-text">
Last updated 2018-06-06 05:22:28 MDT
Last updated 2018-06-15 11:48:51 MDT
</div>
</div>
</body>
......
Workflow changes
================
:icons: font
:toc:
:sectnums:
:sectnumlevels: 2
This document lists changes to the pkg-go workflow which the pkg-go team has
agreed on.
This document lists changes to the pkg-go workflow which the pkg-go team
came to a consensus and which Michael Stapelberg summarized
in November 2017.
The discussion began with this email: [pkg-go] Minutes for the DebConf17 BoF:
https://alioth-lists.debian.net/pipermail/pkg-go-maintainers/Week-of-Mon-20170807/014361.html
[IMPORTANT]
.This proposal for workflow changes is still a work-in-progress.
====
`dh-make-golang` has not yet adapted to this new proposed workflow.
For newcomers and the less experienced, myself included, it is recommended
to stick with the old workflow until all the infrastructures supporting
the migration to the new workflow are in place. — AF
====
== 2017-11 changes
......