File: DISTRIBUTIONS

package info (click to toggle)
tinymux 2.12.0.10-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 7,000 kB
  • sloc: cpp: 132,440; sh: 3,225; lex: 1,264; makefile: 238; ansic: 141
file content (62 lines) | stat: -rwxr-xr-x 2,522 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
TinyMUX 2.12: DISTRIBUTIONS
Last Update: July 2012
~~~~~~~~~~~~~~~~~~~~~~

Where you can get TinyMUX 2.12:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

TinyMUX 2.12 is developed by Stephen Dennis (brazilofmux@gmail.com) and a small
group of enthusiastic volunteers.  The server is simultaneously developed on
Windows and Unix platforms.  For the latest version, updates, and news, please
look at any of the project websites:

  ftp://ftp.tinymux.org/TinyMUX
  http://www.tinymux.org


Release Information:
~~~~~~~~~~~~~~~~~~~

Server development for TinyMUX is done by the scheme as listed below.
These numbers will be reflected by the result of typing 'VERSION' on
the game

2.x.x       Major or potentially major change in project direction such as a
            new primary maintainer.  For example, David Passmore was
            responsible for the 1.x series, and Stephen Dennis is responsible
            for the 2.x series.

2.1.x       A single release cycle of a set of features.  Typically, there is
            one every year and the version number corresponds to the year in
            which the development occurred.  For example,

                  Years       Version
                1998-2000       2.0
                   2001         2.1
                   2002         2.2
                   2003         2.3
                   2004         2.4
                2005-2006       2.6
                   2007         2.7
                2008-2009       2.9
                2010-2011       2.10
                   2012         2.12

2.x.1       Feature Change.  After Beta has started, the third number
            indicates a change in the feature set -- usually the addition of
            features, but it could also be the removal of a feature.  During
            development, the third number is zero (0).

2.x.x.x     Bug release, build number, or patch to an existing release.  These
            will be released as needed to fix bugs in a format useable to the
            'applypatch', 'patch', and 'dopatch' utilities.


Typically, development for each release cycle begins in January.  After twelve
months, it will usually enter a beta period and stay there for three or four
more months before being released.  Typically, after a year or two, a release
is obsoleted by a later cycle.  So, usually, there are two or three release
cycles being developed and supported at the same time.

Every release cycle consists of an uninterrupted series of patches through
development, beta, release until obsolescence.