Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: steven.monsees@baesystems.com
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #yocto methodology to port from older yocto revisions to current
Date: Mon, 19 Oct 2020 13:29:22 +0200	[thread overview]
Message-ID: <20201019112922.l6d4c42sf2hwrpyg@qschulz> (raw)
In-Reply-To: <MADEUP.163F60F774955E72.8803@lists.yoctoproject.org>

Hi Steve,

On Mon, Oct 19, 2020 at 11:22:41AM +0000, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
> 
> Hello:
> 
> I am currently at Yocto release "Rocko 2.4.1" and I am looking into the effort to port to the latest Yocto release...
> 
> We have been using this  rocko platform revision for the last few years in a project, and now want to move to the latest supported release.
> 
> Is there a preferred established methodology/guidelines when porting projects from much older established revisions of Yocto?
> 

You have a few of the changes highlighted in:
https://docs.yoctoproject.org/ref-manual/migration.html

Obviously, you'd need to do all the changes between Rocko and the
version you're targetting (highly recommend dunfell (3.1) as it's an
LTS).

> Is it considered better to port an established project directly to a new Yocto release, or to slowly migrate the yocto revision to the desired release ?
> 

I've done one upgrade only (krogoth 2.1 to thud 2.6) and it was direct,
I'm not sure there's any benefit in doing incremental upgrades?

Good luck :)
Quentin

  reply	other threads:[~2020-10-19 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 11:22 #yocto methodology to port from older yocto revisions to current Monsees, Steven C (US)
2020-10-19 11:29 ` Quentin Schulz [this message]
2020-10-19 11:49   ` [yocto] " Alexander Kanavin

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=20201019112922.l6d4c42sf2hwrpyg@qschulz \
    --to=quentin.schulz@streamunlimited.com \
    --cc=steven.monsees@baesystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox