Short bio: Computer Scientist, FOSS supporter (read more)
Tux Machines (TM)-specific
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.