-
Notifications
You must be signed in to change notification settings - Fork 440
Rework documation regarding DT discontinuation #3244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
rcooke-warwick
commented
Oct 23, 2025
|
|
||
| A device type will be discontinued based on a set of criteria detailed below, in combination with the judgement of our team: | ||
| - The device manufacturer ends support and sale of the device. This includes discontinuation of sales, as well as BSP support. This would be grounds for immediate discontinuation. | ||
| - The device type has been on the platform for at least 2 years, with little to no usage. Rougly around 100 devices is the current minimum requirement |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have come up with the 100 devices number as a rough guide based on the previous project to create the framework. All the device that have poor scores, and/or we intuitively said that they should be removed, happen to have < 100 devices, so it felt like a safe number. Especially after 2 years.
If 100 devices / 2 years is too generous (I think it might be) then please comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i would remove the "Rougly around 100 devices is the current minimum requirement"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think its probably too generous, I would say a device that hasn't gained traction in the thousands (>1k) is considered poor adoption and would be grounds for discontinuation. That of course excludes those on Custom Device Support plans of course, where they get discontinued when the CDS plan stops being paid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rahul-thakoor @shaunmulligan , I think that >1000 is too harsh. It would leave us with about 18 public device types, which is a good number - but a decent number of those are legacy device types that took years to build up those numbers between various users.
I would propose splitting the difference and saying 500
| - If it is a private device type and the customer has stopped paying for the device to be supported. | ||
|
|
||
|
|
||
| ##### List of discontinued device types |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we discussed, here is a draft list of devices to be discontinued "immediately" - i.e at the end of the cycle. This list is the "burn with fire" list, that have very few (<100 , but most of them 0) paid users.
Please comment on any that you disagree on
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few comments
|
|
||
| A device type will be discontinued based on a set of criteria detailed below, in combination with the judgement of our team: | ||
| - The device manufacturer ends support and sale of the device. This includes discontinuation of sales, as well as BSP support. This would be grounds for immediate discontinuation. | ||
| - The device type has been on the platform for at least 2 years, with little to no usage. Rougly around 100 devices is the current minimum requirement |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think its probably too generous, I would say a device that hasn't gained traction in the thousands (>1k) is considered poor adoption and would be grounds for discontinuation. That of course excludes those on Custom Device Support plans of course, where they get discontinued when the CDS plan stops being paid.
| - `CTI Photon Xavier NX` | ||
| - `PocketBeagle` | ||
| - `Raspberry Pi 400` | ||
| - `Revolution Pi Connect` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably chat to Thomas about the Revolution Pi boards, I think we might want to partner more closely with them and for that reason it might be better to keep their portfolio of devices around, but its probably not major.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the main reason for killing these 2 revolution pi boards was that they aren't available to buy any more.
| - `Nanopi Neo Air` | ||
| - `NanoPi R2C` | ||
| - `NPE X500 M3` | ||
| - `Nvidia Jetson Xavier NX Devkit SD Seeed ReSpeaker-2Mic` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this 2 separate products accidentally merged into one line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for checking, but it's this device https://docs.balena.io/reference/base-images/devicetypes/#:~:text=Nvidia%20Jetson%20Xavier%20NX%20Devkit%20SD%20Seeed%20ReSpeaker%2D2Mic
495442a to
cccf581
Compare
Change-type: patch Signed-off-by: Ryan Cooke <[email protected]>
…nity support section
cccf581 to
6fd4a63
Compare
6fd4a63 to
f10f10e
Compare