Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hanzoku]

This looks interesting, but I'll have to wait for a public demo to show up to judge it properly.

[Dohon]

I also believe that this is looking interesting. Very interesting.

[jester]

FTL is currently pre-Alpha, and is planned for a PC, Mac and Linux release in mid-2012.
For now the game is only playable by IGF and other competition judges. There are no plans for a closed/open beta at this time.

Bah, the devs are scum.  STAND STILL AND ILL JUDGE YOU ALRIGHT

But yeah, interested.

[GreatJustice]

This looks a LOT like Weird Worlds.

[forsaken1111]

Meh, update us when there is a download link. Until then I don't care.

[dogstile]

Edit: I'm pretty sure I was looking at something else when I posted that

Anyway: Want!

[inteuniso]

Man, this game looks awesome.

[Stargrasper]

I feel people don't understand how the tech_demo-alpha-beta-release versioning system works these days. Then again maybe it's I who doesn't undersand it...

No, you're right on both ends.  Not only do most people not understand it, but you don't either.

Pre-alpha - Anything and everything that takes place before testing begins.
Alpha - From pre-alpha until feature freeze.  This is the first phase of testing and features may still be added during this time.
Beta - Begins when feature complete.  This is where most of the bug testing will take place.
Release Candidate - Has potential to be the final product.  Begins after leaving one or more betas.  Most bugs that will be fixed are.  No more bugs will be fixed except fatal errors.
RTM - "Release to Manufacturer".  The software is distributed to manufacturers or marketers.  It isn't yet available for retail.
GA - "General Availability".  The point when the software is available to everyone.

Thank you to Wikipedia for reminding me of the very specific details of how this works.  A large number of things that are said to be pre-alpha when they're actually alpha or beta, because they've likely started testing by the time they tell us about it.  Some might be RC.  A large number said to be beta are actually alpha, because they're still adding features.  People should understand RC, but seem to not.  People don't seem to understand RTM exists.  GA is essentially what we call "release".

[burningpet]

Funny thing is, before i even noticed this game a guy on our forums (towns) have suggested we make a mod that will turn towns into a game somewhat like this only on board a pirate ship.

[Goron]

I feel people don't understand how the tech_demo-alpha-beta-release versioning system works these days. Then again maybe it's I who doesn't undersand it...

No, you're right on both ends.  Not only do most people not understand it, but you don't either.

Pre-alpha - Anything and everything that takes place before testing begins.
Alpha - From pre-alpha until feature freeze.  This is the first phase of testing and features may still be added during this time.
Beta - Begins when feature complete.  This is where most of the bug testing will take place.
Release Candidate - Has potential to be the final product.  Begins after leaving one or more betas.  Most bugs that will be fixed are.  No more bugs will be fixed except fatal errors.
RTM - "Release to Manufacturer".  The software is distributed to manufacturers or marketers.  It isn't yet available for retail.
GA - "General Availability".  The point when the software is available to everyone.

Thank you to Wikipedia for reminding me of the very specific details of how this works.  A large number of things that are said to be pre-alpha when they're actually alpha or beta, because they've likely started testing by the time they tell us about it.  Some might be RC.  A large number said to be beta are actually alpha, because they're still adding features.  People should understand RC, but seem to not.  People don't seem to understand RTM exists.  GA is essentially what we call "release".

Annnnd to *truly* understand a release cycle you would know that none of what your wrote is set in stone and can therefore be ignored. ^_^

[ndkid]

Annnnd to *truly* understand a release cycle you would know that none of what your wrote is set in stone and can therefore be ignored. ^_^

The terms and what they mean are not set in stone, no, in the way that words like "stone" also are not. We have a living language. But in the sense that words have generally recognized meanings, those definitions are fair. A company can use terms however they like, of course, much like how I could use "foo" to mean "I want a steak now", but it's generally accepted that when they or I use a term in an uncommon way, the attempted communication is much more likely to fail.

[Deadmeat1471]

Gotta love bay 12, full of kids trying to justify their existance by 'out experting' each other on things they are far from experts on 

Good game though, looks really promising!

[Stargrasper]

I wasn't trying to out-expert anyone.  If you actually looked at that Wikipedia link I posted, it links directly to the Wikipedia page on Software Release Cycles.  Everything I posted is paraphrased from either that page or some other related site.  I never claimed to understand it and I did cite my source.  My last comments were based on the technical definitions of the words.  Bay12 likes to make mountains out of molehills (sometimes literally, in the context of DF), and a lot of times it feels like this community is conspiring against me when considering some of the attacks against my credibility.

[Shadowgandor]

Meh, I'd say those attacks are more because you're correcting people as well. Just let it go and you're a lot better off

[kulik]

It would be great if you could design your own ships.