# Is meta-mender 'scarthgap' stable enough to migrate from 'kirkstone'?

**URL:** <https://hub.mender.io/t/is-meta-mender-scarthgap-stable-enough-to-migrate-from-kirkstone/7329>\
**Category:** General Discussions\
**Tags:** scarthgap, meta-mender\
**Created:** [November 16, 2024, 3:32am UTC](https://hub.mender.io/t/is-meta-mender-scarthgap-stable-enough-to-migrate-from-kirkstone/7329 "2024-11-16T03:32:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nomtor0204](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/nomtor0204/32/2355_2.png) [@nomtor0204](https://hub.mender.io/u/nomtor0204)\
**Post date:** [November 16, 2024, 3:32am UTC](https://hub.mender.io/t/is-meta-mender-scarthgap-stable-enough-to-migrate-from-kirkstone/7329/1 "2024-11-16T03:32:04Z")

</div>

Hello,

Is the meta-mender branch “scarthgap” stable enough at this point? I’m trying to decide whether I should stick with “kirkstone” until “scarthgap” becomes stable or migrate to “scarthgap” now.

I couldn’t find any mention of meta-mender and “scarthgap” in the [Mender client and Yocto Project version compatibility table](https://docs.mender.io/overview/compatibility#mender-client-and-yocto-project-version).

Also, I noticed a [5.0.x branch](https://github.com/mendersoftware/mender/tree/5.0.x) in the Mender Client GitHub repository. Does this mean that a 5.0.x release is planned for the future, and “scarthgap” will use 5.0.x, with 4.0.x no longer being maintained long-term?

Thank you for your insights!

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [November 16, 2024, 12:42pm UTC](https://hub.mender.io/t/is-meta-mender-scarthgap-stable-enough-to-migrate-from-kirkstone/7329/2 "2024-11-16T12:42:06Z")

</div>

Hi @nomtor0204,

The `scarthgap` branch is definitely stable and ready for production. The compatibility page not being up to date is an oversight, apologies. Will fix that real soon!

Concerning the 5.0.x branch on Client, the official release notes will be out in the upcoming days. But as an early explanation, it is about semantic versioning. We are [moving the `docker`, `script`, `deb` and `rpm` Update Modules out of the main repository](https://github.com/mendersoftware/mender/commit/5b9691ae17e4b3d8724978bb5e809e7af9b8b9c6), which be technical definition is a breaking change. Hence Client version needs to see a major bump, even if there are only comparatively minor changes.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![nomtor0204](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/nomtor0204/32/2355_2.png) [@nomtor0204](https://hub.mender.io/u/nomtor0204)\
**Post date:** [November 16, 2024, 1:10pm UTC](https://hub.mender.io/t/is-meta-mender-scarthgap-stable-enough-to-migrate-from-kirkstone/7329/3 "2024-11-16T13:10:46Z")

</div>

Hi @TheYoctoJester ,

Thank you for your prompt reply!

I’m relieved to hear that “scarthgap” is stable, and I’ll proceed with migrating to it.  
I also appreciate the information regarding the breaking changes in Mender Client 5.0.x.

Best regards,