Language Selection

English French German Italian Portuguese Spanish

On Gentoo Releases and stuff

Filed under
Gentoo

When I got more involved with Gentoo, the release team was aiming to release the then-pending release (2007.1) in early December. Eventually, that date slipped time and again. It was decided to drop the entire release and do a new one (2008.0). Again, the dates kept slipping. Now, the question is why a release is slipping time and again.

* It's not quite as simple as it may seem. Building release media in itself isn't easy to begin with - catalyst is a powerful but complex (and complicated) tool. I got kind of dropped into cold water with release building for alpha (probably because I was the one who didn't have a chair when the music stopped). catalyst build errors can be notoriously hard to debug. On top of this, the central release coordinator has to keep in mind all of the gritty details of the arches that will see release media. There's arches like ppc which also have a differently-bitted cousin (ppc64); there are arches that are very, very slow when building stuff (MIPS). On top of that, some software just doesn't build on some arches (no Java on alpha, for example) which can make deciding what to put on the LiveCD very hairy. This also stresses one point: without the help and expertise of the arch teams, building a release is completely impossible. Some arches are more motivated to get a release out, some less so. Some are notoriously understaffed when it comes to release building, some have too few machines to test the releases (or no physical access, which is just as bad).

* People have lives. This is one that bit us this time: life struck at a very bad point (not that the event had been any better post-release). This occupied the time of a dev for a prolonged time. It made painfully obvious that in some spots, stand-in personnel wasn't there. Let me stress this lest I get misunderstood: such things happen and that the dev in question saw tending to the event as more important than get a release done is his prerogative and not to be questioned. That there wasn't a stand in to keep stuff going (even at a slower pace) is something that needs to be fixed.

More Here




More in Tux Machines

Slackware Live Edition – on its way to 1.0?

Last week the second Beta of the upcoming Slackware 14.2 was released. My goal was to have a new Beta of my liveslak ready by that time, so that I could provide new ISO images to test the Slackware Beta2 on a live medium. Unfortunately, there was an attack of the flu in my team at work and things got a bit busier than usual. There was a plus side to this: some last moment bug fixes which could be applied to my scripts – the result of having more evenings available to test. Therefore the new release is not labeled “0.5.0” but “0.5.1” Read more

Leftovers: KDE

  • Cantor migrating to Phabricator: which tools our contributors must to use
    Projects and software developed by KDE community are going to migrate for a new tool to manage our code, commits, reviews, tasks, and more. This tool is Phabricator and you can visit the instance for KDE projects in this address. Since November 2015 we are migrating Cantor to Phabricator. After our first successful review code some days ago, I decided to write a post about which tools our contributors must to use while the migration process is not finished.
  • Kdenlive's sprint report
    Last week-end, Vincent and me met in Lausanne for a Kdenlive sprint. One of our goal was to merge Gurjot Singh Bhatti's GSoC work on curves for keyframes. This was more work than expected and we spent many hours trying fix the curves and make keyframes behave correctly. Not much time was left for sleep, but we still managed to get outside to make a group (!) picture in the woods above Lausanne.
  • Jekyll 3.x
    I’ve found three different types of transition issues (it is cool to look at these in a project I do not upgrade on a daily basis like Plasma and the rest of the KDE software).
  • kdev-python on Windows: try it!
    I spent the last two or three days playing around with KDE on Windows, with the aim of getting my Python language plugin for KDevelop to run there. In the end, it wasn’t that hard to get this to work — not as hard as I would have expected it to be, anyways.

Manjaro ARM launched

Hi community, wonderful news in regard of architecture expanding within Manjaro Linux. It all started with a simple post on our developers mailing list. Somebody wants to do Manjaro for ARM … Just after one month of development our first alpha release is now ready. So what is this all about? Manjaro Arm is a project aimed to bring you the simplicity and customability that is Manjaro to ARM devices. These devices are growing in numbers and can be used for any number of applications. Most famous is the Raspberry Pi series and BeagleBoard series. Read more

Plasma 5.5.4 and Calligra Suite 2.9.11 now available

The 4th update for KDE's Plasma 5.5.x series is now available to all Chakra users. According to the release schedule, unless new issues occur, this will be the last update for this series before 5.6 gets released next month. Plasma 5.5.4 as usually includes a month's translations and bugfixes, with the authors highlighting the improvements for handling multi-screen setups. The Calligra Suite also receives a bugfix update to version 2.9.11, which mainly provides fixes for krita and kexi. Read more