Language Selection

English French German Italian Portuguese Spanish

LibreOffice: Focus on Design and LibreOffice 6.2 RC2

Filed under
LibO
  • LibreOffice 6.2 community focus: Design

    LibreOffice 6.2 is due to be released at the end of this month, and many communities in the project have been working hard on new features. Today we talk to Heiko Tietze, The Document Foundation’s UX designer, about the upcoming release…

  • LibreOffice 6.2 RC2 is ready for testing

    The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 6.2 RC2 is ready for testing!

    LibreOffice 6.2 will be released as final at the beginning of February, 2019, being LibreOffice 6.2 RC2 the forth pre-release since the development of version 6.2 started in mid May, 2018. See the release plan. Check the release notes to find the new features included in this version of LibreOffice.

    LibreOffice 6.2 RC2 can be downloaded from here, and it’s available for Linux, MacOS and Windows.

More in Tux Machines

today's howtos

Android Leftovers

Rules for product managers at open source companies

Product management is an interesting career. It's immensely rewarding to be the interface between users, business strategy, engineering, and product design. And it's also a highly lucrative career with increasing demand for ambitious and empathetic practitioners. It's also a role with no single path. You might see various certifications and courses emerging to help address the serious skills shortage. The good news is that these are starting to contribute to the talent pipeline, but they struggle to address the wider demands of the role. This is especially the case where roles require direct experience across the enormous range of what it takes to build and ship successful products. Read more

How we decide when to release Fedora

Open source projects can use a variety of different models for deciding when to put out a release. Some projects release on a set schedule. Others decide on what the next release should contain and release whenever that is ready. Some just wake up one day and decide it’s time to release. And other projects go for a rolling release model, avoiding the question entirely. For Fedora, we go with a schedule-based approach. Releasing twice a year means we can give our contributors time to implement large changes while still keeping on the leading edge. Targeting releases for the end of April and the end of October gives everyone predictability: contributors, users, upstreams, and downstreams. But it’s not enough to release whatever’s ready on the scheduled date. We want to make sure that we’re releasing quality software. Over the years, the Fedora community has developed a set of processes to help ensure we can meet both our time and and quality targets. Read more