Greetings, glorious adventurers! If you're joining in our Alpha One spot testing, please follow the steps here to see all the latest test info on our forums and Discord!
Options

What are the different stages of development?

For those of you who don't know what the stages of game development are:

 Pre-alpha refers to all activities performed during the software project before testing. These activities can include requirements analysis, software design, software development, and unit testing. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the functionality is complete. Alpha

 The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white-box techniques. Additional validation is then performed using black-box or gray-box techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.[2]

 Alpha software can be unstable and could cause crashes or data loss. External availability of alpha software is uncommon in proprietary software. However, open source software, in particular, often have publicly available alpha versions, often distributed as the raw source code of the software. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete. Beta

 Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. It generally begins when the software is feature complete. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it.

The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software, willing to test the software, often without charge, and often receiving the final software free of charge or for a reduced price. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, prototype, technical preview / technology preview (TP), or early access. Some software is kept in perpetual beta—where new features and functionality are continually added to the software without establishing a firm "final" release.

 Release candidate

 A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug. A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities. Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product. Beta testing is conducted in a client's or customer's location and to test the software from a user's perspective.

Comments

  • Options
    Formating this text would be a big help reading it...
  • Options
    1: You really need to use paragraphs and returns.

    2: The stages of development you've listed are really obsolete. That's te old waterfall model. Most software development currently uses the Agile model.

    3: In the Agile model, the product basically goes through mini-versions of alpha, beta, testing, release every week or every month. 

    4: Alpha is supposed to be the state of the product where features are still being developed.
    Beta is supposed to be the state of the game where all the features are implemented and the only changes made are to fix bugs.
    Release is supposed to be when all the bugs that are going to be fixed are fixed. And the product is ready to be sold to the consumers.

    Clearly that is not the current model since these days, consumers commonly pay for games during pre-alpha.
    Alpha and Beta are now just obsolete terms used to gate how many players will be let into early access.
    Even some devs are now beginning to refer to opening early access as a successful release.
    These days bug fixes and new features continue to be added after release.
    Many games never make it past early access. Even though thousands of consumers are playing the game.

    Alpha just means you get the earliest access to play the game.
    Beta is the middle phase of access.
    "Release" is when access is no longer restricted - anyone who pays can play.

  • Options
    This is what they mean when they say "brick of text". LOL
  • Options
    I'm quite sure this is the finest example of a "brick of text" I've ever had the opportunity to lay my eyes on.
Sign In or Register to comment.