| Summary: | Add Ubuntu 16.04 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Armin Kuster <akuster> |
| Component: | core | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, meta.mr.watcher, meta.watcher, mhalstead |
| Version: | 2.2 | ||
| Target Milestone: | 2.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Armin Kuster
2016-06-23 14:49:04 UTC
We can replace Ubuntu 1510 with Ubuntu 16.04 Friday July 1st. Does that sound good? (In reply to comment #1) > We can replace Ubuntu 1510 with Ubuntu 16.04 Friday July 1st. Does that > sound good? I am good with it. Been using 16.04 in my own builds for a month now. Do we archive older OS's? I wipe the builder and re-provision with a new distro. I don't know what I would archive as I haven't in the past. This may be a non-sequitur but I refer to SANITY_TESTED_DISTROS in http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-poky/conf/distro/poky.conf for any given commit to see which distro's are supported. I'm not sure if that is correct. I've made the autobuilder changes and started the refresh but I'm still working out the templates. This will be available tomorrow. Not today after all. New estimate is 4 July. The AB is usable in the meantime. Done and tested. |