<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Robie,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Indeed, this is a great idea that could
be used in other teams. I have been wanting a more automated way
of updating the Ubuntu Studio bug subscriptions. And I would
rather not build something special.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If I was to create the Ubuntu Studio
bug subscription list in the yaml file from scratch, I would want
to take the package names from the Package Set, which is also in
Launchpad. Maybe a function to compare the two and propose a
commit with new packages from the package set? But are the team
names the same in both cases?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Just food for thought.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Regards,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Ross</div>
<div class="moz-cite-prefix"> <br>
</div>
<div class="moz-cite-prefix">On 12/14/21 4:53 PM, Robie Basak wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20211214155309.GD23236@mal.justgohome.co.uk">
<pre class="moz-quote-pre" wrap="">Dear Archive Team,
On the Server Team, we've started to use git to manage our team
subscriptions to packages in Launchpad. The main reasons are:
1) To avoid inadvertent changes - we lost a bunch of subscriptions by
accident at one point.
2) To keep an audit trail of changes made.
This is particularly important for the server team as we have an
effective bug triage process now that is able to stay on top of all new
bug traffic for all our subscribed packages. Accidentally losing a
subscription causes bug traffic to miss our bug triage process, which
includes tracking new activity on previously triaged bugs.
We're achieving this with the script at this repository, which also
contains our canonical list of subscriptions:
<a class="moz-txt-link-freetext" href="https://git.launchpad.net/~canonical-server/+git/team-subscriptions">https://git.launchpad.net/~canonical-server/+git/team-subscriptions</a>
The script just ensures that Launchpad's view matches our "officially
subscribed" list that we keep there in git. Changes made in Launchpad
that aren't committed in git get reverted automatically.
The requirement from us is simply that the git repository be updated
with any changes to our subscriptions with a suitable commit message to
provide an explanation. Otherwise changes intentionally get reverted.
When I arranged this, it didn't occur to me that anybody other than us
touches our package subscriptions on Launchpad. But apparently you do,
when making changes for technicalities like versioned source package
names (see below for the thread with an example). I didn't even realise
that you had an ACL that permitted you to do so directly, thinking that
the request always went via our team in the past.
However if your expectation is that you can JFDI in Launchpad itself,
then this clashes with our desire for the audit trail.
On the other hand, I don't expect to be forcing this onto other teams,
and so having a different workflow for you to follow depending on which
team it is will also clearly be a pain.
Any suggestions on how to proceed?
Note that the script is deliberately generic and so other teams could
adopt it too if they wish. And of course we can move the repository
and/or provide ACLs to relevant other teams as needed.
Robie
On Mon, Dec 13, 2021 at 09:04:54AM -0800, Steve Langasek wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Mon, Dec 13, 2021 at 07:31:16AM +0000, Robie Basak wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Sat, Dec 11, 2021 at 10:19:12AM -0800, Steve Langasek wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Sat, Dec 11, 2021 at 08:00:23AM +0000, <a class="moz-txt-link-abbreviated" href="mailto:robie.basak@canonical.com">robie.basak@canonical.com</a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The following subscriptions are superfluous:
php8.1
Superfluous subscriptions removed
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Please revert this, I subscribed the server team to php8.1 so it could be
promoted and unblock php-defaults in -proposed.
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Done.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Sorry this broke your workflow. We need any changes to our subscriptions
to be committed to git now[1]. I'm not sure how to make this less
painful for you next time, save for asking us instead of making the
change directly.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Any suggestions?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""><a class="moz-txt-link-freetext" href="https://git.launchpad.net/~canonical-server/+git/team-subscriptions">https://git.launchpad.net/~canonical-server/+git/team-subscriptions</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
As I happen to be subscribed to ubuntu-server and see these emails, it's easy
enough for me to follow up to confirm. I don't think all members of the
Ubuntu Archive team are subscribed to this list, and I'm sure they're not
aware there's been a Server Team-specific change to the promotion workflow.
I'd suggest that you promulgate this to the Archive Team
(ubuntu-release@lists) so that there's awareness and we can discuss how best
to integrate this into the workflow.
In the meantime I'd just ask that when your scripts detect a mismatch, the
Server Team be proactive about following up to figure out why the mismatch
was there.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer <a class="moz-txt-link-freetext" href="https://www.debian.org/">https://www.debian.org/</a>
<a class="moz-txt-link-abbreviated" href="mailto:slangasek@ubuntu.com">slangasek@ubuntu.com</a> <a class="moz-txt-link-abbreviated" href="mailto:vorlon@debian.org">vorlon@debian.org</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">--
ubuntu-server mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ubuntu-server@lists.ubuntu.com">ubuntu-server@lists.ubuntu.com</a>
<a class="moz-txt-link-freetext" href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-server">https://lists.ubuntu.com/mailman/listinfo/ubuntu-server</a>
More info: <a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/ServerTeam">https://wiki.ubuntu.com/ServerTeam</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
</blockquote>
<p><br>
</p>
</body>
</html>