[SOLVED] KiCad packages by major version

[esberard]

Hello,

A colleague has suggested a package for KiCad software.

Normally, we should create a separate package for each major version.
So, tis-kicad7, tis-kicad8, and tis-kicad9 for the future.

Reasons:
– Until now, this has been the case: when installing a new major version, it didn't uninstall the old one.
– We shouldn't automatically upgrade to a major version because many plugins aren't updated simultaneously in the KiCad repositories.
– This could be disastrous, especially since some manufacturer plugins for automatic deployment would no longer work.
– Some projects don't migrate well from one major version to the next, so it's always a good idea to keep a previous version (n-1) just in case.
– New major versions are often buggy despite the work of beta testers (another reason to keep a previous version (n-1)).

Sub-releases after .xxx can be applied automatically.

Thank you for your consideration.

Rémy

[dcardon]

Hi Rémy,

I'll pass this message on to the packaging team. We're not experts on every app in the store, so please don't hesitate to report any issues you have. However, this is a priority, and if it's urgent, please submit a support ticket.

Best regards,

Denis