All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Klein <matthias.klein@optimeas.de>
To: "chanho61.park@samsung.com" <chanho61.park@samsung.com>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>,
	"steve@sakoman.com" <steve@sakoman.com>
Subject: AW: [yocto] Question of Yocto dunfell LTS period
Date: Fri, 14 Jan 2022 07:14:53 +0000	[thread overview]
Message-ID: <AM0PR10MB3107F4F770A4DDDDAAD009A099549@AM0PR10MB3107.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <000801d808e3$fcea94e0$f6bfbea0$@samsung.com>

Hello together,

I would like to add a question to the topic:

Why was the LTS period for dunfell extended?
Can we expect the same for kirstone?

Many greetings,
Matthias

-----Ursprüngliche Nachricht-----
Von: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> Im Auftrag von Chanho Park via lists.yoctoproject.org
Gesendet: Freitag, 14. Januar 2022 02:14
An: yocto@lists.yoctoproject.org; openembedded-core@lists.openembedded.org
Cc: richard.purdie@linuxfoundation.org; steve@sakoman.com
Betreff: [yocto] Question of Yocto dunfell LTS period

Dear folks,

I found the lts period of Yocto dunfell has been extended from 2022.04 to 2024.04[1].
AFAIK, a Yocto LTS version has 2 years period. I tried to find any notice regarding this but I just found Richard's e-mail[2] in last year.
Can I find any thread or notice regarding this extension?

[1]: https://wiki.yoctoproject.org/wiki/Releases
[2]:
https://lore.kernel.org/yocto/3878e27fb895718b8c5d65f444fea443a56e0587.camel
@linuxfoundation.org/

Best Regards,
Chanho Park


  parent reply	other threads:[~2022-01-14  7:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220114011350epcas2p16efb8acbdc4d9edceee83569e10cc359@epcas2p1.samsung.com>
2022-01-14  1:13 ` Question of Yocto dunfell LTS period Chanho Park
2022-01-14  1:36   ` [OE-core] " Jate Sujjavanich
2022-01-14  5:28     ` [yocto] " Michael Opdenacker
2022-01-14  9:42       ` Alexander Kanavin
2022-01-14 12:41         ` Zoltan Boszormenyi
2022-01-14 17:39           ` Ross Burton
2022-01-14  7:14   ` Matthias Klein [this message]
2022-01-14 13:04     ` AW: [yocto] " Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM0PR10MB3107F4F770A4DDDDAAD009A099549@AM0PR10MB3107.EURPRD10.PROD.OUTLOOK.COM \
    --to=matthias.klein@optimeas.de \
    --cc=chanho61.park@samsung.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=steve@sakoman.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.