| Summary: | Customise BitBake and layer versions in a project | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Belen Barros Pena <belen.barros.pena> |
| Component: | toaster | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alexandru.damian, belen.barros.pena, bluelightning, cristiana.voicu, david.reyna |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | GUI design pending | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Belen Barros Pena
2014-08-21 11:18:57 UTC
From Alex: On 21/08/2014 12:38, "Damian, Alexandru" <alexandru.damian@intel.com> wrote: I'm gonna try to summarize my thoughts here. Maybe we should define a "Release" as - a release is a default template for populating project settings once a project is created, any change in the project settings may be performed, without affecting the original template; The bitbake version is part of the "release", and part of the project settings; Clearing 2.0 milestone The current fixture model covers this, where the lastest two stable branches are offered, plus master and local. |