Revision history [back]

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch could have been very handy and very important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch could have been very handy and very important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch could would have been very handy and very important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch would have been very handy and very important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch would have been very handy and very important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

*Note*Note from April 19th:* would be really nice to get some answer from Jolla to this question. Maybe I'm wrong, and it's technically not feasible, or too expensive, or it's a stupid idea...

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch would have been very handy and very important:important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

*Note from April 19th:* would be really nice to get some answer from Jolla to this question. Maybe I'm wrong, and it's technically not feasible, or too expensive, or it's a stupid idea...

I would like to know whether some kind of patch management for small and specific improvements or bug fixing is being considered. It would be very useful specially for urgent security patches, but also for fixing issues or broken updates.

While regular OS updates are great in terms of extending functionality (thank you for this!), there are two recent cases where a mass distribution of a small binary patch would have been very handy and very important:

• The OpenSSL bug, which was luckily addressed a few days later with the monthly OS update. But what would have been the scenario, if no update had been planned?
• The broken functionality of WPA2 Enterprise (aka "eduroam" WiFi access), which doesn't work anymore since the last update. Not to blame Jolla, but it would be great to get a patch for this quite important feature (even if it used to be a command line hack).

I perfectly understand that you can't deploy a full, several hundred megabytes large OS update across all countries every time (and it will happen more and more often) some security or other issue arises, this requires a lot of planing and testing of the whole system. But providing a flexible and simple mechanism for quickly distributing small mandatory (security) or optional (functional) patches could be essential or at least a differentiating argument for the trust and the survival of the whole Jolla project.

*Note from April 19th:* would be really nice to get some answer from Jolla to this question. Maybe I'm wrong, and it's technically not feasible, or too expensive, or it's a stupid idea...