From: Ian Lynagh Date: Sat, 23 Jun 2007 22:44:40 +0000 (+0000) Subject: Update version numbering policy in the users guide X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=commitdiff_plain;h=147c8d2ec47fab14fd0386e10e73f1a4da005442 Update version numbering policy in the users guide --- diff --git a/docs/users_guide/intro.xml b/docs/users_guide/intro.xml index d4b6a12..7216942 100644 --- a/docs/users_guide/intro.xml +++ b/docs/users_guide/intro.xml @@ -319,18 +319,18 @@ GHC version numbering policy version, of ghc - As of GHC version 6.0, we have adopted the following policy + As of GHC version 6.8, we have adopted the following policy for numbering GHC versions: Stable Releases - These are numbered x.y.z, where - y is even, and - z is the patchlevel number (the trailing - .z can be omitted if z - is zero). Patchlevels are bug-fix releases only, and never + Stable branches are numbered x.y, where + y is even. + Releases on the stable branch x.y are numbered x.y.z, where + z (>= 1) is the patchlevel number. + Patchlevels are bug-fix releases only, and never change the programmer interface to any system-supplied code. However, if you install a new patchlevel over an old one you will need to recompile any code that was compiled against the @@ -341,8 +341,8 @@ x.y.z is the integer xyy (if y is a single digit, then a leading zero - is added, so for example in version 6.2 of GHC, - __GLASGOW_HASKELL__==602). + is added, so for example in version 6.8.2 of GHC we would have + __GLASGOW_HASKELL__==608). __GLASGOW_HASKELL__ @@ -350,28 +350,52 @@ - Snapshots/unstable releases + Stable snapshots - We may make snapshot releases of the current - development sources from time to time, and the current - sources are always available via the CVS repository (see the - GHC web - site for details). - - Snapshot releases are named - x.y.YYYYMMDD - where YYYYMMDD is the date of the sources - from which the snapshot was built. In theory, you can check - out the exact same sources from the CVS repository using - this date. - - If y is odd, then this is a - snapshot of the CVS HEAD (the main development branch). If - y is even, then it is a snapshot - of the stable branch between patchlevel releases. For - example, 6.3.20040225 would be a snapshot - of the HEAD, but 6.2.20040225 would be a - snapshot of the 6.2 branch. + + We may make snapshot releases of the current + stable branch available for download, and the latest sources are available from the darcs repositories. + + + Stable snapshot releases are named + x.y.z.YYYYMMDD. + where YYYYMMDD is the date of the sources + from which the snapshot was built, and x.y.z+1 is the next release to be made on that branch. + For example, 6.8.1.20040225 would be a + snapshot of the 6.8 branch during the development + of 6.8.2. + + The value of __GLASGOW_HASKELL__ + for a snapshot release is the integer + xyy. You should never write any + conditional code which tests for this value, however: since + interfaces change on a day-to-day basis, and we don't have + finer granularity in the values of + __GLASGOW_HASKELL__, you should only + conditionally compile using predicates which test whether + __GLASGOW_HASKELL__ is equal to, later + than, or earlier than a given major release. + + __GLASGOW_HASKELL__ + + + + + + Unstable snapshots + + + We may make snapshot releases of the + HEAD available for download, and the latest sources are available from the darcs repositories. + + + Unstable snapshot releases are named + x.y.YYYYMMDD. + where YYYYMMDD is the date of the sources + from which the snapshot was built. + For example, 6.7.20040225 would be a + snapshot of the HEAD before the creation of the + 6.8 branch. The value of __GLASGOW_HASKELL__ for a snapshot release is the integer