Can't determine which patches in upstream branches have been released with specific snap versions

Bug #1798920 reported by Tony Espy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snappy-hwe-snaps
Confirmed
Undecided
Unassigned

Bug Description

While working on network-manager snap bug #1797191, I needed to recommend to the customer which version of the snap to update to. Looking at the git repository for our network-manager snap:

https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager

I realized that there's no easy way to determine which git commits the upstream branch (in this case origin/network-manager/xenial/1.2.2) have been released in a specific version of the snap, as we only tag the master branch.

We should at minimum, be using a source-commit attribute in snapcraft.yaml to pin to a specific commit, and probably be adding tags to the upstream branches to make it even clearer. Updating the top-level ChangeLog file would also be a good idea, as it this file is updated automatically when new versions of a snap are released.

Tony Espy (awe)
Changed in snappy-hwe-snaps:
status: New → Confirmed
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.