Over the past few months, Ubuntu Studio has been in the process of migrating from Canonical’s servers to a new host with a deadline of today.
-
Over the past few months, Ubuntu Studio has been in the process of migrating from Canonical’s servers to a new host with a deadline of today. It took some time to come up with the proper host as we wanted a 1:1 solution. We eventually found that solution, and three weeks ago started the migration process.
-
Over the past few months, Ubuntu Studio has been in the process of migrating from Canonical’s servers to a new host with a deadline of today. It took some time to come up with the proper host as we wanted a 1:1 solution. We eventually found that solution, and three weeks ago started the migration process.
However, after multiple delays on Canonical’s end getting us what we needed to start the migration, which we only got yesterday, the website was shut-off today, which was the initial deadline Canonical’s Information Services (IS) team gave us to have the migration complete initially, but said they would extend due to the delays. Apparently that was not the case.
-
However, after multiple delays on Canonical’s end getting us what we needed to start the migration, which we only got yesterday, the website was shut-off today, which was the initial deadline Canonical’s Information Services (IS) team gave us to have the migration complete initially, but said they would extend due to the delays. Apparently that was not the case.
From our end, IS has been deprioritizing community efforts and has been hindered by certain decisions, and now Ubuntu Studio has fallen victim to bad decisions that have left us homeless. We are in the process of asking Canonical to turn the server back on for a few days while migration work, which was underway, restarts.
-
From our end, IS has been deprioritizing community efforts and has been hindered by certain decisions, and now Ubuntu Studio has fallen victim to bad decisions that have left us homeless. We are in the process of asking Canonical to turn the server back on for a few days while migration work, which was underway, restarts.
Furthermore, IS refuses to communicate directly with anyone on the Ubuntu Studio team, among other teams. We have sent ticket after ticket, and the only way we can get communication through is by going through the Canonical Community Team. This makes it feel like anything we do is met with hostility and futility because we are unable to do anything from our end.
-
Furthermore, IS refuses to communicate directly with anyone on the Ubuntu Studio team, among other teams. We have sent ticket after ticket, and the only way we can get communication through is by going through the Canonical Community Team. This makes it feel like anything we do is met with hostility and futility because we are unable to do anything from our end.
With that, we hope you find patience and understanding as we try to get this situation sorted. We’re not happy about it, but please, understand the blame here isn’t on the Ubuntu Studio team.
-
With that, we hope you find patience and understanding as we try to get this situation sorted. We’re not happy about it, but please, understand the blame here isn’t on the Ubuntu Studio team.
-
With that, we hope you find patience and understanding as we try to get this situation sorted. We’re not happy about it, but please, understand the blame here isn’t on the Ubuntu Studio team.
To clarify, it doesn’t affect .iso images, package repositories, or anything like that. Ubuntu Studio isn’t a separate distribution, after all.
