What sort of problem is the current release tarball creating? It already includes the vendor/ directory, which means you don’t need to hand craft it and can already use that tree in CentOS. For cases you really don’t want the vendor/ tree – which may create issues due to version drift – you can just delete it.
For one, patches don’t cleanly apply to the regular release tarball, due to missing Git files. This may hopefully become less of a problem in the future, but for now, it’s an issue.
i386 local run gave errors (http://paste.ubuntu.com/24362377/) probably because of network connectivity issues during the execution, retriggered (will updated this post later with the results)
Status update, I’ve moved part of the validation done at the candidate stage to beta, so that we have stronger validation earlier and not promote potentially invalid snaps. The tests moved to beta are the automated suite execution on instances with the core snap refreshed from the revision in the last stable image to the new core, currently running, I’ll post here the results.
Hello Ara, the validation is good so far and we have the description of the process executed previously at the candidate stage, hopefully the snaps will be promoted to candidate very soon. I’ll post here any status change.
We are planning to promote to candidate tomorrow morning. From there we will document the testing cycle and release to stable after a call for testing and subsequent results. Let us know if you have hard deadlines or are looking for a particular feature in this release and we can work on a more specific timeline for you.