| Summary: | yocto-announce template still references meta-gplv2 | ||
|---|---|---|---|
| Product: | [Infrastructure] Release Process | Reporter: | kweihmann |
| Component: | Release Process | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | chee.yang.lee, randy.macleod, richard.purdie, ross.burton |
| Version: | 4.1.1 | ||
| Target Milestone: | 4.1 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
kweihmann
2022-09-26 06:01:27 UTC
few questions, 1. i assume this affect only release from 4.1 onwards, right? 2. should we keep the artefacts for meta-gplv2 (for 4.1 onwards) ? i think Autobuilder still prepare them during RC build 3. YP 3.1 and YP 4.0 will still do release with meta-gplv2, right? (In reply to comment #1) > few questions, > 1. i assume this affect only release from 4.1 onwards, right? Correct. > 2. should we keep the artefacts for meta-gplv2 (for 4.1 onwards) ? i think > Autobuilder still prepare them during RC build We should not. > 3. YP 3.1 and YP 4.0 will still do release with meta-gplv2, right? Correct. I've had a try at fixing this: https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?id=effb9b0fcdb9b26086903abecc207464d4e3a341 although I think we could do with something with less hardcoding ideally. FYI, the 4.1 release announcement didn't mention meta-gplv2: https://lists.yoctoproject.org/g/yocto-announce/message/259 With RP's changes to YP AB, can we close this issue? Fixed as per previous comments. |