| ... | @@ -102,12 +102,10 @@ happens in the release cycle: |
... | @@ -102,12 +102,10 @@ happens in the release cycle: |
|
|
|
|
|
|
|
|
|
|
|
|
- Throughout the year: discuss and refine proposals
|
|
- Throughout the year: discuss and refine proposals
|
|
|
- Review period (a 2-week period around September-October): committee chooses which addenda to include
|
|
- The committee will meet in February, May, August and November. They will review proposals completed before that month, and make a decision about which to accept
|
|
|
- Following the review period:
|
|
- After the committee has met, the decisions will be announced on the mailing list
|
|
|
|
|
- In January of the following year, the committee chair will produce a revision of the language standard by incorporating the accepted proposals
|
|
|
- Announcement of accepted proposals
|
|
- A new [committee](committee) will then be formed
|
|
|
- Form a new [committee](committee)
|
|
|
|
|
- The committee chair/co-chair produce a revision of the language standard by incorporating the accepted proposals
|
|
|
|
|
|
|
|
|
|
## Major revisions
|
|
## Major revisions
|
|
|
|
|
|
| ... | @@ -124,10 +122,9 @@ needed for textbooks, for example. |
... | @@ -124,10 +122,9 @@ needed for textbooks, for example. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We expect releases to be made late in the year, around
|
|
We expect releases to be made early in the year, normally during January.
|
|
|
October-November. Hence, each release will be named after the year
|
|
Each release will be named after the year of the release.
|
|
|
following the year of release. For example, the language revision
|
|
For example, the language revision released in January 2014 will be named "Haskell 2014".
|
|
|
released in November 2009 will be named "Haskell 2010".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Compiler support
|
|
## Compiler support
|
| ... | | ... | |