Init:
✔ Run snapcraft init with an existing .snapcraft.yaml file.

Parser:
✔ Run the parser using a part defined in .snapcraft.yaml

Plugins and snaps:
✔ Build a rust snap.
✔ Build a python2 snap and check that the pyc files are removed.
✔ Build a python2 snap and check that the shebangs use env.
✔ Build a python3 snap and check that the shebangs use env.
✔ Build a snap with a oneshot daemon.
✔ Build a snap using the godeps plugin.
✔ Run the ROS example snap in xenial.
✔ Build mhall's Arduino IDE snap.
✔ Build the OS snap, check the file ownership.
✔ Build kernel snaps with debarch targets.

Autocomplete:
✔ Autocomplete with register, tour, push, release, prime, update, define, 
search.

Store:
✔ Run the integration tests using the staging store.
✔ Run the integration tests using the production store.

Exploratory:
✔ Build snaps using the go plugin.
✔ Build snaps using the dump plugin.

✗ Packaging:
* Install snapcraft in a virtualenv using the requirements files.
* Run the tests in a virtualenv using the requirements-test file.
There is still work to do here, but not a blocker for this release: bug #1611498
This is not related to the package in xenial, just affects the developer 
experience from master. The work done in this milestone gets us closer to work 
nicely in a virtualenv, which wasn't working before, so not are regression 
either.

I'm going to mark this bug as verified. Thanks Steve!

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611009

Title:
  [SRU] New stable micro release 2.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1611009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to