{"id":3742,"date":"2019-05-02T16:42:26","date_gmt":"2019-05-02T15:42:26","guid":{"rendered":"https:\/\/blog.linuxmint.com\/?p=3742"},"modified":"2019-05-02T17:03:47","modified_gmt":"2019-05-02T16:03:47","slug":"monthly-news-april-2019","status":"publish","type":"post","link":"https:\/\/blog.linuxmint.com\/?p=3742","title":{"rendered":"Monthly News – April 2019"},"content":{"rendered":"

Last month we talked about what it was like to develop free software and I shared some thoughts about the team, our work and our relationship with the community. I want to thank you all for your amazing response and the support you gave us. I don’t think we’ve ever received that many emails, comments and messages and that many encouragements. I didn’t expect it to be that big but here it is, it’s huge, right in front of us and we’ll always be able to look back at it whenever, if ever, we’re in doubt, you’re here for us, and you love our work. I’ve seen many people come here and post their very first comment after years of just reading the blog just to say they enjoyed what we were doing. That means a lot to me, I’m sure it means a lot to other users and developers too and all the people who contribute to Linux Mint. I wasn’t exactly looking for TLC when making this post last month, and we’re not “depressed” (as we could read in some blogs on the Internet), I wanted to address some points and spread the word a little more on what it was like for us as well… but I’m glad it was interpreted as it was, I’m glad the news was covered outside of our community and I’m really touched by your response to it. Thank you so much for this.<\/p>\n

Last month I think I also talked a tiny bit too much about what was going on within the team. On the one hand it is part of my role to report on the progress being done, on the other hand we’re dealing with individuals, there are people involved, efforts being made, feelings which can be hurt and it’s part of my role also to protect that. If something won’t work out, we part ways, if something can’t make it in, we postpone it or reject it but when that happens I’m not sure we should necessarily talk publicly about it. There isn’t anyone involved who doesn’t want the best for Linux Mint and we all share the same goal, we all want more features, less bugs and an amazing new release. How we get to that isn’t always smooth and we can’t always agree on everything, but we’re a team and so I might mention individual names when things are great, but I hope you’ll understand I don’t when things don’t work out. We’ll face these issues together as a team and I don’t want anyone to feel bad or get the feeling that it’s their fault. Trying to help, no matter what the outcome is, is a great thing. You can’t be blamed for trying, especially not in public and I don’t want anyone to feel like they need to justify themselves one way or another.<\/p>\n

Looking ahead I feel very comfortable again. Some issues are still on the horizon, there is uncertainty about some of the large things we’ve been working on (for me personally this includes the website and logo redesign), but we’ve reaffirmed what was important to us. We will get a great 19.2 release, no matter what, and we’ll enjoy working on it.<\/p>\n

Server issues<\/strong><\/p>\n

The server issues we experienced at the beginning of April should hopefully be over. They were caused by power and capacity issues in one of the datacenters we’re using.<\/p>\n

Developer Guide<\/strong><\/p>\n

The Developer Guide is ready. It describes the projects we work on, the technologies we use, and explains how to get set up, how to build packages and how to alpha-test. If you’re interested in development and you want to get involved this is a must read.<\/p>\n

The guide is available in English, in HTML, PDF and ePub at https:\/\/linuxmint-developer-guide.readthedocs.io\/en\/latest\/<\/a>.<\/p>\n

Let us know if you think anything isn’t clear or if you feel something is missing. We’ll add more content within the guide as we go along, not only as an introduction to newcomers but also as a reference for best practices.<\/p>\n

Mint 17.x reached EOL<\/strong><\/p>\n

After 5 good years of service, Linux Mint 17.x (i.e. 17, 17.1, 17.2 and 17.3) reached “End Of Life”. Although the repositories will continue to work they will no longer receive security updates.<\/p>\n

If you are running Mint 17.x, you can install Timeshift from the repositories, prepare system snapshots and plan to upgrade to Mint 18 using this tutorial: https:\/\/community.linuxmint.com\/tutorial\/view\/2316<\/a>.<\/p>\n

Don’t hesitate to ask for help or to report issues so we can get you to version 18 safely.<\/p>\n

Samba<\/strong><\/p>\n

With every new package base we experience regressions. This was key in our decision to stick to LTS and it helped us focus on development while underneath, the base we were using for 5 years could continue to mature. This decision boosted our development pace and increased the quality of our distribution. When with Linux Mint 19 we jumped to Ubuntu 18.04, along with the many improvements and new software versions, we also inherited regressions, some of them quite frustrating to users: Wine, scanner and printer, and Samba to name a few.<\/p>\n

These kind of issues are common on new package bases and they happen often in rolling distributions or in non-LTS releases. They eventually get fixed, in these rolling distributions and non-LTS releases first and then the fix usually gets backported to the LTS base.<\/p>\n

This hasn’t happened with Samba yet. When something important we don’t maintain doesn’t work properly, and it’s been a while, we usually consider pinning it. In other words we look at whether or not we can backport a newer version which fixes the issue, or bring back an earlier version which didn’t suffer the issue. In the case of Samba this is not possible, not only because of Samba’s complexity and large number of dependencies (it just doesn’t easily compile like that across bases) but also because pinning this package in Mint would be a maintenance issue due to the number of vulnerabilities found in Samba and how often it receives security updates.<\/p>\n

Samba supports different communication protocol versions. In Mint 18.x Samba 4.3 was mostly using a protocol version called NT1 which worked well and continues to work well. After Windows was badly affected by ransomware attacks, Microsoft decided to retire NT1 and the Samba team worked on switching more towards some of the newer protocol versions such as SMB2 and SMB3. These changes created regressions and Ubuntu is currently in the process of trying to tackle them.<\/p>\n

Two of the most important issues are reported on Launchpad at:<\/p>\n