Update README with enhanced information and communication channels #1769
Conversation
otavio
requested review from
dv1,
kraj,
angolini,
gibsson,
quaresmajose,
zandrey,
junzhuimx,
thochstein,
chrisdimich and
a team
|
LGTM
Em qua., 13 de mar. de 2024 16:32, Khem Raj ***@***.***>
escreveu:
… ***@***.**** approved this pull request.
Lgtm
—
Reply to this email directly, view it on GitHub
<#1769 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL7BKBLOVYBMNMBEZ2KUGLYYCSTJAVCNFSM6AAAAABEUWJVQKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMZVGA2TAMZVGM>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
| - **Yocto Project LTS Releases:** Our LTS branches follow the Yocto Project LTS release schedule, which involves a four-year maintenance period. A new LTS version is typically released every two years. | ||
| - **Stable Releases:** We aim to provide stable releases every six months, aligning with the pace of Yocto Project's stable releases. | ||
|
|
||
| ## Contributing |
There was a problem hiding this comment.
I've seen that people still occasionally use meta-frescale ML. Shall this be mentioned here in any form (e.g., patches, discussions, etc.), or a note that ML is not used and shall be sunset?
There was a problem hiding this comment.
It'd be good to sunset it and adopt the GitHub Discussions.
There was a problem hiding this comment.
I've said in email replies to the mailing list several times that we are migrating the conversation to github.
I don't understand exactly what "sunset" means here. Is it possible to disable new emails to be sent to the mailing list?
There was a problem hiding this comment.
@rpurdie, can we have it with an automated reply or similar?
There was a problem hiding this comment.
@otavio You mean make the mailing list read only? We can do that
Enhanced the README file by adding detailed maintenance policies for the `meta-freescale` layer, including information about branch management and release cycles. Additionally, included specifics about the maintained branches such as `master`, `scarthgap`, `nanbield`, and `kirkstone`. This update aims to provide users with a clearer understanding of the project's maintenance practices and available branches. Signed-off-by: Otavio Salvador <[email protected]>
Enhanced the README file by adding detailed maintenance policies for the
meta-freescalelayer, including information about branch managementand release cycles.
Additionally, included specifics about the maintained branches such as
master,scarthgap,nanbield, andkirkstone. This update aims toprovide users with a clearer understanding of the project's maintenance
practices and available branches.
Signed-off-by: Otavio Salvador [email protected]